Build a UK customer communications shortlist around real journeys

Start with the handover that currently loses customers

Choose three journeys from your own business before asking for demonstrations. A service company might use a new enquiry, a quotation follow-up and a renewal reminder. A retailer might choose newsletter signup, an abandoned basket and a repeat purchase. Record the trigger, source of customer information, next action, responsible employee and successful outcome. This becomes the same brief for every supplier. It also shows whether you need a CRM, a campaign tool, a customer inbox or several connected products. Buying one broad platform is useful only if the required handovers actually work.

• Choose a normal case, an exception and a customer who withdraws permission.
• Use invented test contacts and representative order data.
• Name an owner for each step and for each failed integration.

Test behaviour, not a list of channel names

For email, ask the demonstrator to build a rolling audience of people who clicked a named campaign but have not bought. Make a test purchase and inspect whether the contact leaves the group. Then run a timed welcome journey with separate paths for a click and a purchase. For SMS, inspect a reply, an unsubscribe, a failed delivery and the bill for a longer message. For WhatsApp, examine number onboarding, template approval and the transfer from automation to a staff member. These are different operational questions, even when the supplier sells all three channels.

• Ask for recipient-level events rather than dashboard totals alone.
• Confirm whether the exact workflow is native, an integration or custom work.
• Keep the proposed subscription visible during the demonstration.

Compare the UK commercial offer

Request a written price for the same contact count, monthly sends, users, message destinations and support needs. State whether you need a branded sender or a reply-capable UK number. Ask whether tax is included and which currency will appear on invoices. Do not convert an international headline price and present it as a supplier's UK offer. Esendex publishes a GBP starting package, while other providers use contact configurators or destination-based calculators. Compare the resulting annual cost, including migration, onboarding, integration maintenance, number rental and overages.

• Model a normal month and a seasonal peak.
• Record the term, renewal basis and cancellation process.
• Separate subscription, messaging and implementation charges.

Ask AI to complete a useful task

Give each product the same brief: draft an email for a known audience, explain a performance change, or suggest whom to contact next. Inspect the source information, editable output and any action taken. Copy generation, predictive timing and autonomous execution are separate capabilities. An assistant that drafts a journey may still require manual content and filters, as Brevo documents. Klaviyo's channel-affinity feature requires at least two active channels. Record these prerequisites alongside the result so a feature's existence does not become a promise about your account.

• Request English output using your actual brand constraints.
• Ask which plan and quota the demonstration uses.
• Retain human review for messages and changes until the pilot proves reliable.

Finish with evidence, ownership and an exit plan

Treat an unanswered question as unknown, not proof that the product lacks the feature. Keep supplier confirmations separate from public documentation and from tests your team actually completed. Ask who will maintain suppression rules, handle permission changes, review processing arrangements and approve campaign access. Export a small sample of contacts, relationships and engagement events before signing. Finally check that the shortlisted brand is current: Textlocal Messenger closed in July 2026, and MessageMedia now appears under Sinch Engage. A directory should reflect those changes rather than inflate choice with duplicate or retired products.

• Keep a dated evidence sheet with a source for every scored requirement.
• Make unresolved mandatory requirements a purchase condition.
• Schedule a pilot review before committing the whole customer database.

Explore the comparisons