A two-way WhatsApp inbox connected to the Cloud API, plus click-to-chat fallbacks, itinerary sharing, campaign broadcasts and email templates — all logged against the right query.
Connect the Meta WhatsApp Cloud API and your team replies from inside TraWe, with threads matched to queries by phone number.
Send an itinerary as formatted text or a branded PDF, plus invoice and client-portal links — and the quotation flips to Sent automatically.
Segment by destination, season or spend and broadcast offers, then track who opened and replied.
IMAP/SMTP brings supplier and traveller email into the CRM, with branded templates for every event.
Payment reminders, trip-start wishes and document requests trigger on schedule without anyone remembering.
The mobile view opens with the contact list first, so agents can work the inbox on the move.
Add your WhatsApp Cloud API credentials, or start with click-to-chat links.
Reply from the dual-pane inbox; every message is stored on the query timeline.
Push itineraries, invoices and portal links in one tap.
Broadcast seasonal offers to past travellers and route replies back into the pipeline.
For the two-way inbox, yes — the Meta Cloud API. Without it, TraWe falls back to click-to-chat links that still log the intent.
Yes, matching is done on the last ten digits of the phone number, so country-code variations still resolve.
Yes — itinerary and invoice PDFs, or long-form formatted text up to WhatsApp's limit.
Yes, an IMAP/SMTP inbox plus branded templates for quotations, invoices, reminders and trip updates.