Agent templates
AI agent templates for WhatsApp
Base prompts ready to copy, with the tools each agent needs, the questions to test that it works and how to set it up in Meteor.
What instructions should I give a WhatsApp AI agent?
A good WhatsApp AI agent template defines six things: the role (who it is and which business it serves), the tone, what it does step by step, what it never does, when it hands the conversation to a person and which details it asks the customer for. Your business specifics go separately, as information the agent looks up.
These templates were written by Meteor’s editorial team based on what works in real WhatsApp conversations. They work on any agent platform; in Meteor, each one also says which integration fulfils each tool.
Last updated
Agent templates
The templates, by use case
Customer service
What instructions should I give a customer service agent?
See the template →Sales and lead qualification
How do I write the prompt for a WhatsApp sales agent?
See the template →Restaurant orders
What should the prompt of a restaurant ordering chatbot say?
See the template →Bookings and appointments
What instructions does an appointment booking agent need?
See the template →Online store order status
How do I set up an agent that answers order status questions?
See the template →Friendly collections
How should a collections agent talk on WhatsApp?
See the template →After-sales support
What does an after-sales support agent do and how do you instruct it?
See the template →Real estate front desk
What do I tell an AI agent that serves a real estate agency’s prospects?
See the template →Clinic and practice
What can a clinic’s AI agent do, and what must it never say?
See the template →Education enrollments
How do I instruct an agent that handles enrollments for a school or academy?
See the template →Agent templates
The six parts of every template
If your prompt does not answer these six questions, the agent will answer them on its own, and not the way you would like.
- 1
Role
Who the agent is, which business it serves and what its main task is. One task per agent.
- 2
Tone
Formal or informal, message length and how many questions per message.
- 3
What it does
The steps in order, and what it checks before answering: menu, calendar, order or invoice.
- 4
What it does not do
What it never invents or promises. It is the section that prevents the most mistakes.
- 5
When it hands over
The exact cases, and the summary it leaves so the customer repeats nothing.
- 6
Details it asks for
Only the necessary ones, all in one message and not one at a time.
FAQ
Questions about the templates
Yes. They are written in plain language and do not depend on Meteor: they describe capabilities (check the calendar, register the customer, send a payment link) rather than tool names. What changes from one platform to another is which integration fulfils each capability.
No. The prompt says how to behave; the business information (catalog, prices, opening hours, policies) and the integrations give it the data. Without that data, a good agent says it does not know instead of inventing.
Long enough to cover the six parts, which in these templates is between 200 and 300 words. Longer is not better: what matters is clear rules, especially about what it does not do and when it hands over to a person.
With the five questions in each template, plus two you know are hard in your business. In Meteor you do it in the test conversation, which simulates a customer without going through WhatsApp.
Set up your first template in Meteor
Book a live demo and watch the Mets of Meteor working on your own operation.