How to choose an automation vendor: a checklist
Picking an automation vendor feels a lot like hiring someone you will only meet twice before they start touching your systems. You get a sales call, a demo, maybe a proposal with a few screenshots, and then you are expected to sign. Most of what actually determines whether the project works, how they handle a broken integration, whether anyone still answers after month three, never comes up in that first conversation unless you ask for it directly. The checklist below is built around the questions that tend to matter later, not the ones that are easy to answer in a pitch.
Start with the problem, not the platform
Before you look at a single vendor, write down the actual workflow you want fixed, in plain language. Not "we need AI" but "customers message us on WhatsApp and Instagram, someone copies the details into a spreadsheet by hand, and half the time a lead sits untouched for a day." A vendor worth hiring should be able to repeat that problem back to you in their own words after one call. If they skip straight to features, pricing tiers, or a generic AI pitch without asking what breaks today, that is worth noticing early.
Ask what happens when something goes wrong
Every automation breaks eventually. A CRM changes its API, a message format shifts, a holiday schedule throws off a trigger. The question that separates a real implementation partner from a reseller is simple: what happens the week after launch when something stops working? Is there a support channel with a response time attached, or just an email address that might get checked. Ask for a concrete example of a past client issue and how it got resolved, not a general assurance that "we're always available."
Get clear on who owns the data and the account
This one gets skipped constantly and causes real pain later. Who owns the WhatsApp Business account, the chatbot configuration, the integration credentials, you or the vendor? If the vendor builds everything inside their own proprietary account and the relationship ends, can you take your setup with you, or does it disappear. A vendor confident in their own work will not flinch at putting data ownership and exportability in writing. One who hesitates is telling you something.
Check how they handle multiple languages, if that matters to you
For a business operating in Hebrew, Russian, and English, this is not a nice-to-have. Ask to see an actual conversation flow in each language, not just a claim that the system "supports" them. There is a real difference between a bot that translates responses mechanically and one that was actually built with native phrasing for each audience. A quick way to test this: ask the vendor to show you a transcript, in the target language, of the bot handling an edge case, like a customer changing their mind mid-conversation.
Ask for a realistic timeline, and what counts as done
"Launch in one to three weeks" shows up a lot in this industry, and it can be true for a narrow, well-scoped piece of work. It usually is not true for a full CRM integration with custom routing logic. Ask the vendor to break the timeline into phases: what ships first, what depends on your team providing information or access, and what "done" actually means for each phase. A vendor who gives you a single number with no breakdown is either underestimating the work or hoping you will not ask again once the invoice is paid.
Look for a human handoff, not full replacement
Be wary of anyone promising the automation will handle everything with no human involved, ever. Real automation setups have a clear boundary: the bot answers routine questions, collects the right details, and hands off anything complex, urgent, or emotionally loaded to a person, with the context carried along so the customer does not repeat themselves. Ask the vendor to walk you through exactly where that handoff happens in their system, and how a customer actually reaches a human when the bot cannot help.
Talk to someone who is already a client
A vendor should be able to connect you with at least one existing client, even briefly, especially one in a similar industry or using a similar channel setup. If every reference is a glowing one-line testimonial with no name attached, that is a gap worth asking about directly. A short call with someone who has lived with the system for three months tells you more than another hour of demo.
Confirm pricing covers more than the first month
Ask what the ongoing cost looks like after launch, not just the setup fee. Does the price change if message volume grows. Is there a cost for adding a new channel or language later. Vendors differ widely here, and a lower upfront number sometimes hides a steeper second-year bill. Get this in writing before you sign, not as a verbal reassurance during the sales call.
Where to start
Got a repetitive process eating up hours?
Tell us about it in a couple of lines and we will show you how automation would work on your own data.
Get in touch