Telegram Integration
Use a Telegram group to receive restaurant notifications. The installation's bot must be configured and running before a location can receive messages.
Before you start: ask the installation operator for the bot's username. You need restaurant administrator access, a location, and an API key assigned to that location. Only the installation operator configures the bot service itself.
Link a group to a location
The automatic linking process reads a group title containing the location's API key when the bot first discovers that group.
Prepare the group before adding the bot
The group title contains a credential. Use a private staff group and keep its membership limited to authorized people. Configure the title before adding the bot; changing it afterward may not trigger another automatic linking attempt.
- In OrderNow, open API Keys and copy the key for the intended location.
- In Telegram, create a private group with the staff who should receive notifications.
- Set its title to
Group name|API key, replacing the second part with the copied key. Do not add spaces around the|separator. - Add the bot identified by your installation operator.
- In OrderNow, open Locations, edit the same location, and check the Telegram chat ID field.
Result: successful automatic linking fills the location's Telegram chat ID. The linking code does not send a confirmation message, so use the saved field and a controlled test to check setup.
Check delivery
- Confirm with the operator that a test session/order will not cause unwanted cash-register or kitchen work.
- Start a test table session at the configured location and check for the new-session notification.
- If needed, place an agreed test order and check the group for its notification.
- Ask the operator to investigate if the chat ID is present but no message arrives.
The application sends new-session and placed-order notifications through the configured location. Check failures and cash-register processing in Tables and Messages; Telegram delivery is not a receipt that the cash register processed an order.
Change or disable the destination
Each location stores one Telegram chat ID. Generating another API key for the same location does not create separate kitchen, bar, or manager notification subscriptions.
To replace the destination, ask the installation operator to confirm the new group ID, then update Locations → edit location → Telegram chat ID and save. An already configured location is not automatically reassigned by adding the bot to another group.
To stop messages for the location, clear its Telegram chat ID and save the location. Coordinate this with staff who rely on the group. There is no Telegram toggle on the current Messages page.
Troubleshooting
| What you see | What to check | Next action |
|---|---|---|
| Telegram chat ID remains empty | Bot username, group title format, key's location, and whether the title was set before adding the bot | Give the installation operator the location and setup sequence. Ask them to verify linking; avoid repeatedly changing keys or groups. |
| The location already has a chat ID | Whether it points to the intended group | Have the operator verify the destination before replacing it. |
| Chat ID is saved but no notifications arrive | Whether the bot service is enabled and can send to that group | Ask the operator to check the bot service and permissions. |
| A notification arrives but the order is not processed | The table's order state and register connection | Follow Messages → Failed orders and commands. |
When asking for help, include the location, test time, and whether the chat ID was saved. Do not include the API key or a screenshot of a group title containing it.