Wrike
Your receptionist can create a Wrike task when a caller needs a follow-up, with a title and a short summary of the conversation. Reception connects through Zapier, so you can pick the Wrike folder from a list. Wrike’s own API needs a folder ID that isn’t shown in the Wrike app.
Your receptionist creates the task during the call, from what the caller said up to that point. It isn’t Reception.ai’s post-call summary email. Add a procedure so the task is created at the end of the conversation, as shown below.
Set up
Add the Wrike action
In your Zapier MCP server at mcp.zapier.com, add the Wrike Create Task action and connect your Wrike account. Set the fields as listed in Actions.
Assign the tool
In Reception.ai, open the Zapier integration’s Tools tab, select Refresh tools, and assign the Wrike action to the Client (receptionist). Assign it to the Assistant too if you want to create tasks yourself by chatting with your business assistant.
Add a procedure
Open Teach your receptionist and add a procedure, for example:
Trigger: When the caller needs someone from our team to follow up.
Steps:
Type @ to insert the Wrike action as a reference.
Test it
Test your receptionist by asking for a callback about a quote. The task appears in the folder you chose.
Actions
Create a follow-up task
Keep Parent Folder fixed, so a caller can’t steer tasks into other folders. If Zapier offers more fields for your account, such as an assignee, set those to fixed values too.
Zapier’s Wrike connection acts as the Wrike user who connected it. Only add the Create Task action for your receptionist. Search or update actions would let callers ask about other work in your Wrike account.
Limitations
- Tasks are created from what was said during the call. If a caller hangs up before your receptionist creates the task, no task is made. Ask your receptionist to create the task as soon as it has the details.
- The task’s author is the Wrike user who connected Zapier.
- Each action your receptionist runs uses tasks from your Zapier plan. Zapier currently counts two tasks per successful call; failed calls aren’t counted. When the plan runs out, the action stops until it resets.