The questions serious buyers ask.

SayTrip supports calls, in-person advisory conversations, email and WhatsApp. It can also process existing recordings. Phone-system ingestion and the exact capture flow depend on the customer setup and are agreed during scoping.

Relevant context becomes sourced information across four connected levels: the conversation, the current trip, the long-term traveller profile and patterns across your own portfolio. New inputs can create or update profiles; authorised users can review and correct the result.

Neither description alone is accurate. A note-taker produces text; SayTrip produces sourced, reusable traveller context. Teams can use SayTrip Workspace as their traveller CRM or enrich an existing CRM or PMS through a scoped integration.

SayTrip currently supports fourteen language variants: English (US, UK and India), German, French (France and Canada), Italian, Spanish (Spain and US), Portuguese (Brazil), Japanese, Korean, Hindi and Simplified Chinese. We confirm the required languages and capture setup during scoping.

The advisory conversation remains the centre of the workflow. SayTrip structures relevant context afterwards, so advisors do not have to recreate the same information in notes and CRM fields. Capture, review and system hand-offs are agreed during rollout.

Subject to role-based permissions, authorised colleagues can use the existing profile, travel history and sourced context. The relationship no longer depends on one person’s memory.

We first agree scope, users, capture flow, permissions and integrations. A group can start with one branch or unit, validate the workflow and then expand.

Store it, yes — fill it in, no. A CRM is only as good as what gets entered consistently. SayTrip structures context from the conversations themselves, each field tied to its source — and a scoped integration delivers the agreed fields to the CRM without your team typing them again.

REST APIs and webhooks are the standard integration path. Exact schemas, field mappings, destinations and any named connector are agreed during scoping.

A recording starts only after consent. If a traveller declines, SayTrip records nothing; an advisor can still add relevant context manually or leave a post-call voice note.

SayTrip is EU-hosted. Data is encrypted in transit and at rest, production and development environments are separate, and access is role-based.

Authorised users can review, correct or remove context, and every structured fact retains its source. SayTrip does not make automated booking decisions or contact travellers.