Send your WhatsApp leads to your CRM, automatically
Travellers write on WhatsApp, Instagram, Messenger, WeChat, email and your website chat. Your CRM, your sales sheet and your accounting should know about it without anyone typing it again. Fareply sends what happens in your conversations to Zapier, Make, n8n or your own system, within seconds of it happening.
Request access Read the setup guide
What Fareply sends
| When this happens in Fareply | Your tool can |
|---|---|
| A new lead: a traveller writes for the first time, on any channel | Add a row to a Google Sheet or a contact to your CRM, with the channel and, for ads, which ad |
| A quote sent, with the total and currency | Create or update a deal with its value |
| A quote accepted on the quote page | Move the deal forward and tell the person who books |
| A payment link sent or marked paid | Create the invoice or record the payment |
| A booking reference saved | Link the booking in your back office |
| A lead booked or lost, with the reason | Close the deal as won or lost |
| A traveller waiting too long for an answer | Alert a manager in the team chat you use |
Every event carries the conversation: the traveller's name, phone or email, the channel, who it is assigned to, the ad it came from, the booking reference and a link back to the conversation in Fareply.
Set up in three steps, no developer needed
- Get an address from your tool. In Zapier, a Catch Hook trigger; in Make, a Custom webhook; in n8n, a Webhook node.
- Paste it in Fareply. Under Integrations, add a connection and tick the events you want.
- Send a test, then build the rest. Your tool learns the fields from the test event. Add the action you want after it: a row in Google Sheets, a deal in your CRM, a message to your team.
Built not to lose a lead
- Retries. If your tool does not answer, Fareply tries again after 1, 5 and 15 minutes, then for up to a day.
- Paused, not dropped. If a connection keeps failing, Fareply pauses it, emails the owners and keeps the new events. Switch it on again and the waiting events are sent.
- Delivery log. Every event of the last 30 days, your tool's answer, and a button to send one again.
- Signed. Each event is signed, so a developer can check it really came from Fareply.
And the other way: bookings into Fareply
Your booking system can send the booking reference and status back to the conversation, so the traveller gets the confirmation in the same chat. See Booking references and confirmations.
Plans
Connections to Zapier, Make, n8n and your own system are included in Pro, Agency and the DMC plans, up to 5 connections per agency. See pricing.
Questions
Which CRMs work?
Any CRM, sheet or system that Zapier, Make or n8n can reach, or that accepts a JSON request at an https address. The setup guide has the details for developers.
Do we need Zapier if we have a developer?
No. Your developer can give Fareply any https address that accepts a POST, and check each event with the signing secret.
Can one connection send only some events?
Yes. Each connection has its own events. A filter in your tool on the event type also works.
Is Fareply a CRM?
No. Fareply answers enquiries and keeps the conversation, the quotes and the pipeline. Your CRM stays your CRM; Fareply keeps it up to date.