Define your needs, understand connection requirements and compare delivery scope before buying automated replies.
Start with one recurring conversation
List five questions your business receives repeatedly: price, availability, booking, order status and reaching a person. Start with one scenario. Write the approved answer and when to hand the conversation to a human. This turns a vague chatbot request into a testable scope.
What should the offer include?
Confirm the WhatsApp connection, answer source, customer data destination and staff notifications. Specify the required languages and message types. If a seller mentions CRM support, ask which CRM, which fields and whether synchronization works in one or both directions.
Separate implementation from running costs
Ask about the WhatsApp Business API or connection provider, n8n hosting, AI usage and CRM subscriptions. Request an estimate tied to a defined usage level. A workflow implementation fee does not necessarily include these ongoing tools.
Test difficult cases before handover
Use dummy data to test an unknown question, a request for a human, missing details, duplicate orders and a failed spreadsheet connection. Check that the system does not invent prices or confirm a booking before it is saved. Agree who reviews failures after delivery.
When is the service suitable?
The starting point is clearer when your service information is stable, someone owns the conversations and the process is defined. If pricing and terms change frequently, establish the source of truth and escalation process before expanding automated answers.
A quick decision checklist
Clear scope, known requirements, acceptance tests, documentation and someone responsible after handover. Clarify any missing item before buying.
Sources and next step
Review official n8n documentation and N8N Central listings. Use our starting guide to prepare your requirements and read the editorial methodology to understand the limits of this comparison.