01Can Operations confirm Friday delivery?
02I’ve forwarded the WhatsApp message.
03I thought Sales was replying.
04Has anyone confirmed the date?
Customer handoffs across teams
Hand over the work.Know who has it.
Give the next person the context, open question and due time. See who accepted the work—and who needs to update the customer.
FromMaya · Sales
ToRohan · Operations
Customer promise
Confirm Friday delivery for the first 240-unit order
Aarav Mehta · Mehta Stores
- Open point
- Can Operations meet the revised date?
- Due
- Today · 14:30
AcceptedReturn to Maya for the customer reply · 16:00
Everyone was copied
Nobody owned the answer.
A forwarded message shows who was told. It does not show who agreed to act, what they need to decide, or when the customer should hear back.
- Customer waiting for
- Friday delivery confirmation
- Open question
- Can dispatch meet the revised date?
- Owner
- Rohan · Operations
- Due
- Today · 14:30
- Return to
- Maya · Sales
The brief stays linked to the original request. Rohan sees what he needs to decide, and Maya can see when the answer is due back.
01 / Follow one handoff
See how the work changes hands.
Prepare what the next person needs, show who accepted it, and return the result to the person updating the customer.
Choose a stage to see the handoff.
Pass what they need.
Maya adds the customer, current status, open question and due time.
Rohan can review the request without rebuilding the story.- Customer
- Aarav Mehta · Mehta Stores
- Customer waiting for
- Friday delivery confirmation
- Open point
- Can Operations meet the revised date?
- Requested from
- Rohan · Operations
- Due
- Today · 14:30
Prepare
Enough context to decide.
Accept
One person takes responsibility.
Return
The result goes back to the customer contact.
What moves with the work
Pass the context needed to act.
Keep it brief. Link the original request, state what is needed, who has it, when it is due, and where the answer goes.
- 01
Customer waiting for
What the customer needs confirmed or completed.
- 02
What has happened
The current status, with the source attached.
- 03
Open question
The exact decision or action needed.
- 04
Current owner
Who remains responsible until someone else accepts.
- 05
Next step and due time
What needs to happen, and by when.
- 06
Who gets the answer
Who receives the result and updates the customer.
Current product, in context
See the whole handoff.
Three product views show the live request, the customer behind it, and the team responsible for what happens next.
Current product · 01
Can the next person see what needs doing?
The conversation stays with its channel, priority, owner, response time and next action.
View full size 
Scroll horizontally to inspect this capture, or view it full size.
- 01Source conversation
- 02Responsible owner
- 03Response timing and next action
Inbox · Active request
Current product · 02
Can they see the customer behind it?
The customer record keeps communication and recent commercial work close to the request.
View full size 
Scroll horizontally to inspect this capture, or view it full size.
- 01Contact and company
- 02Communication actions
- 03Related commercial work
Customer · Aarav Mehta, Mehta Stores
Current product · 03
Will the request reach the right team?
Team Inbox settings show where the request arrives, which channel is connected, who can see it and what remains unassigned.
View full size 
Scroll horizontally to inspect this capture, or view it full size.
- 01Team destination
- 02Connected route
- 03Unassigned work
Team Inbox · Shared destination
When responsibility changes
Make it clear who has the work.
Assignment, acceptance and collaboration work differently. WRKZY keeps the responsible person visible in each case.
Assign it directly.
A manager can assign work to a direct report with a due date visible in their workload.
- Owner named
- Due date visible
Ask a teammate.
The work stays with you until your teammate accepts the request.
- Accept
- Suggest a date
- Decline
Bring others in.
Comments and followers keep others involved while one person remains responsible.
- Comment
- Follow
- Owner unchanged
Acceptance applies to supported peer task requests. Manager assignments and collaborative comments do not use the same acceptance step.
For handoffs that repeat
Keep routine handoffs moving.
When a handoff follows the same rules each time, choose what starts it, who receives the work, how long it can wait, and what happens if it gets stuck.
- 01
Start with the right event
Use an event and conditions to identify the work.
- 02
Send it to the right person
Choose the team or teammate, next step, and due time.
- 03
Plan for delays
Set a timeout or use Human Handoff when someone needs to decide.
- 04
Test before turning it on
Test the workflow and check where it needs attention.
Current productConfigured workflow
Automation can route repeatable work and show when it needs attention. A person decides what to do when the situation falls outside the rules.
When the supporting work is done
Close the handoff.
Record the result, send it back to the person replying, and keep the final update with the customer record.
Result
Friday delivery confirmed
- Check
- Dispatch capacity confirmed
- Checked by
- Rohan · Operations · 15:18
- Sent back to
- Maya · Sales
- Customer update
- Sent · 15:32
Customer informed · Handoff complete
Start with one handoff
Make the next handoff clear.
Choose a request that moves between teams each week. Decide what information goes with it, who takes the next step, and who receives the answer.
Try it with one real request.
Bring one shared request into WRKZY with the customer, owner, due time, context, and person waiting for the result.
Start free trialWorking across several teams or workspaces?
Talk through migrations, workspace boundaries, response commitments, and repeatable handoffs.
Talk to sales