Design around the languages your customers use

Teams in Cyprus may receive enquiries in several languages, but the mix differs by audience, sector and channel. Before a build, sample the business's own inbox and CRM records, list the languages and channels that matter, and check that approved answers exist in each language the assistant will use. Test routing and hand-off for unsupported or uncertain messages instead of translating them into a commitment the business has not approved.

Plan personal-data handling before choosing a hosting setup

For a workflow that processes personal data, map its purpose, data categories, access, vendors, transfers and retention with the people responsible for privacy and security. GDPR responsibilities depend on the organisation and processing involved; this is technical implementation guidance, not legal advice. Hosting inside the EEA does not by itself make a workflow compliant. Confirm vendor terms and data routes with the accountable privacy or legal owner before selecting the deployment.

Estimate cost and operating coverage

Setup effort depends on channels, connected systems, data quality and approval steps. Ongoing costs can include software licences, hosting, AI or API usage, monitoring and staff time for exceptions. Estimate both typical and peak volume, name the person who owns the exception queue, and agree support hours and recovery responsibilities before the pilot. Request a scoped estimate rather than assuming one price fits every Cyprus business.