Turn WhatsApp Requests into Wrike Tasks
This recipe turns a client’s request in chat into a Wrike task in the right folder, with a complete brief and a due date. Part of connecting Wrike to WhatsApp and AI chat.
What happens today
Clients send briefs on WhatsApp: a voice note, a few screenshots, a deadline mentioned in passing. The account lead forwards them to the team or retypes them into Wrike when there is time. Details get lost, and work starts late because the task did not exist.
The flow that works
- The client asks for new work.
- AeroChat asks for the details your team needs to start, one question at a time.
- It finds the client’s folder in Wrike.
- It creates a task there with the brief, the links and the due date.
- It tells the client the request is in and what happens next.
The recipe
Copy this into AeroChat
When a client asks for new work, follow these steps.
- Ask for anything we do not have yet: their company name, what they need, the deadline, where it will be used and any files or links (example fields).
- Find the folder in Wrike named after their company (example). If there is none, use our New requests folder (example).
- Create a task in that folder. Title: the company name followed by a short name for the work. Description: the brief in short bullet points, the links they sent and a summary of the conversation. Due date: their deadline.
- Tell them the request is in and our team will confirm the timeline within one working day (example).
- If the deadline is within two working days (example), tell them we will check whether we can meet it and hand the conversation to our team.
Ask only for what is missing. Reply in the customer’s language.
Change the folder names and the fields you ask for to match how your team briefs work before you paste it.
What to connect
- Wrike. Create an app in Wrike’s App Console, generate a permanent access token from an account that can see your client folders, and paste the token in when AeroChat asks.
- Your knowledge base. Upload your service details to AeroChat so it can answer questions before it takes the request.
After you paste the recipe, AeroChat builds the workflow as a draft and shows a checklist: connect Wrike, add your knowledge base if the recipe uses one, then switch it on. If it built the connection from Wrike’s public documentation, the checklist asks you to check it once against the current docs.
Using a different system? If it has a public API, it connects to AeroChat the same way: describe what you want, paste in its key, and it runs.
Can’t find your tool? Message us in the chat on this page and we’ll tell you how it connects.
What you still decide
- Which details AeroChat asks for before it creates the task.
- Which folder new requests go into.
- Which deadlines go to a person first.
The result to expect
Every brief from chat is a task in Wrike with the details your team needs, without anyone retyping it. Work starts on the day the client asks.
Measure it with your own numbers: tasks created from chat, and time from request to first update to the client, for a month before and after.
Next: answer project status questions from Wrike.
Works on every chat channel
This workflow runs the same way on WhatsApp, Instagram, Facebook Messenger, TikTok, Telegram, the chat on your website and email, with the same Wrike connection behind it. See what each channel does on the Wrike integration page.
Turn your first chat request into a Wrike task
Paste the recipe, add your Wrike token, and send a test brief in the chat.
Start your 7-day free trial. No credit card needed.
On Shopify? Install AeroChat from the Shopify App Store.
