Clanker CloudClient requests rarely arrive as complete briefs. One email names a deadline, the next adds a deliverable, and a later reply changes the audience. Before work begins, someone has to turn those messages into a clear account of what was requested and what still needs an answer.
A hosted Clanker Workspace Agent can prepare that account using a managed email address and the files in its assigned Project. The first useful deliverable is a brief you can inspect, with proposed scope kept separate from approved work.
Give intake a defined role
Create an Intake Agent for a fictional studio. Its job is to save the requested outcome, source statements, missing inputs, and questions for the owner. Add the studio's intake checklist as reference knowledge and keep each client's actual brief in its Project.
Use instructions such as:
Turn incoming requests into a project intake brief.
Record the requested deliverables, audience, dates, and dependencies.
Quote or identify the source for each material request.
Separate a requested change from approved scope.
Preserve ambiguous dates and missing owners as open questions.
Save the brief in the assigned Project.
Reply with a concise summary and clarification questions.
Do not accept new scope, quote a price, or commit a delivery date.
Test these instructions in a normal Session first. A custom Agent can reuse the intake method without embedding one client's facts into every later request.
Route the request to the intended Project
Managed Clanker addresses are available on Business, Business Pro, and eligible Enterprise accounts, including Unlimited entitlements. Eligible accounts support up to five addresses at email.clankercloud.ai.
Create an address, link the Project and hosted Agent, and save the allowed senders. Their requests then start work automatically without confirmation for each email. Begin with a sender you control and fictional material. The email setup walkthrough explains the account controls and thread behavior.
A shared address does not automatically discover the right client Project from the client's name. Use the configured routing deliberately. Do not put unrelated client material into the same working context just to avoid setting up a clear boundary.
Check a request with conflicting details
Suppose the test sender writes:
Please prepare a launch page and a one-page sales brief for our partner team. We hope to launch next Friday. The images are still with legal, and the approved scope currently covers only the launch page.
The expected intake brief should record:
| Detail | Interpretation |
|---|---|
| Launch page | Covered by the stated approved scope. |
| Sales brief | Requested addition that needs a scope decision. |
| Next Friday | Proposed timing requiring a calendar date and timezone. |
| Images with legal | An unresolved dependency. |
| Partner team | Stated audience for the request. |
Check the saved file in the email Session. A useful response asks whether to add the sales brief and which date is intended. It should not announce that both deliverables have been accepted for Friday.
Continue clarification in the same thread
Replies continue the email Session, so the Agent can work with the conversation already attached to that intake. Ask it to distinguish newly confirmed facts from questions that remain unresolved and to update the saved brief accordingly.
Opening the Session in Workspace keeps email replies enabled. Posting your own message in Workspace permanently converts that thread to a regular Session and stops its email replies. Choose the communication path before continuing.
When the owner approves the brief, use it as the input to the next task: a proposal, launch checklist, or client report. Keep the approval recorded with the project rather than letting the intake Agent infer it from a friendly email response.
Sources
Give your assistant one useful job
Route approved email requests to a hosted Agent with the project context needed to prepare a useful brief.