Update the instructions
- Owner
- Support specialist
- Due
- Thursday
- Done when
- The instructions name the team that handles return requests.
Connect a goal to a project and the project to a department’s work. Employees see what to do next, agents pick up assignments and managers see what is holding the team up.
Explore capabilities ↓A prototype example. The support team clarifies who should receive a return request.
This describes the MyBusiness product design. A first pilot follows one workflow, with its features agreed in advance.
The prototype shows what each person is working on and who is waiting for it. Follow an assignment from the queue through to approval.
In the demo, the reviewer opens the draft alongside its source, then approves the revision or returns it with a comment.
Tell the agent what you need and which sources it can use. It prepares a draft for the assigned reviewer. The prototype shows how to tag an agent with @ in a task discussion.
The CRM prototype connects a deal to its conversation history and next step. Access to your CRM and permission to send messages are agreed separately for the pilot.
The product design includes roles, spending limits and a run log. The pilot checks these requirements against the selected workflow.
The roadmap includes templates for agent instructions and settings that work well for recurring tasks.
Move one recurring job from a paper log or spreadsheet. Record who owns each step, where its materials live and what counts as finished work.
A small team can start with a shared board. At a larger company, work moves across departments and each person sees the material permitted by their role.
The process determines the scope. A minimal workflow includes an assignment, one permitted source, an agent draft, human review and a recorded outcome. Additional modules depend on the task.
Choose work you can compare before and during a pilot, such as checking estimates, reconciling delivery notes or preparing client emails.
How the pilot works