Connect Telegram and LINE
Both take about five minutes and need no help from us. Neither has a reply window: you can answer at any time.
Before you start
- Telegram: a Telegram account on your phone. The bot is free and belongs to that account; use a company phone if you can.
- LINE: a LINE Official Account for your agency (free to create, with paid plans for more messages; the free allowance depends on your country). Create it at LINE Official Account Manager, then enable the Messaging API.
Official guides: Telegram: create a bot with BotFather and LINE: get started with the Messaging API.
Telegram
- In Telegram, open @BotFather and send
/newbot(or/mybotsfor a bot you already have). - Choose a name, for example your agency's name, and a username ending in
bot. - Copy the API token BotFather sends (it looks like
123456789:ABC...). - In Fareply, Channels, Connect a Telegram bot: paste it into Bot token and click Connect.
Share t.me/yourbotname with travellers, or add the username to your website chat. Only private chats
with the bot are read; group messages are ignored.
"Telegram does not accept this bot token": copy it again from BotFather (/mybots, your bot,
API Token). If you created a new token, the old one stops working.
LINE
- LINE Official Account Manager: Settings, Messaging API, enable it.
- LINE Developers console, that channel: on Basic settings copy the Channel secret; on the Messaging API tab issue a Channel access token (long-lived) and copy it.
- In Fareply, Channels, Connect LINE: paste both and click Connect. Fareply sets the webhook address itself.
- Back in LINE Official Account Manager, Settings, Response settings: turn Webhooks on and Auto-response messages off. In LINE Developers, Use webhook must be on.
Replies are LINE push messages and count toward your LINE plan's monthly message allowance. When it runs out, replies show "The LINE account has used its monthly message allowance": upgrade the LINE plan or wait for the next month.
Disconnecting
On Channels, click Disconnect. Past conversations stay in the inbox; the stored token is deleted.