Make is not asking Telegram questions in a chat window — it is running a scenario on a clock and moving the answers into the tools your team already lives in. Each example lists the goal, the Entergram modules that carry it, and what your colleagues see when the run completes. Nobody has to be logged in for any of them to fire, which is the difference between a helpful assistant and an operational process.
The scenario
Every Monday at 09:00, refresh the deal spreadsheet with the current pipeline stage of every active client conversation.
Modules called
entergram_list_workspace_chatsentergram_list_custom_column_optionsentergram_get_chat_custom_fields
The run produces
The options module gives you the human-readable labels behind each stored value, so the sheet reads Negotiation rather than an opaque key. Sales opens one tab on Monday morning and sees the same picture the account managers see in Telegram.
The scenario
Poll the ticket queue every ten minutes and route by severity — critical to on-call, everything else to the team channel.
Modules called
entergram_list_ticketsentergram_list_ticket_custom_columnsentergram_get_ticket
The run produces
The schema module supplies the real option values so your filter compares keys instead of display text, which is the single most common reason a router branch silently matches nothing. Critical tickets reach a phone in minutes; the rest accumulate quietly.
The scenario
When a new contact appears, enrich them from your marketing platform and write the result back onto the conversation.
Modules called
entergram_list_contactsentergram_get_contactentergram_patch_chat_custom_fields
The run produces
A filter drops anyone already enriched so the scenario is safe to run on a tight schedule. Company size, source and lifecycle stage land on the chat record, and the next person to open that conversation sees context nobody typed by hand. Run it once over your back catalogue with the schedule off, then leave it running forward.
The scenario
When a deal is marked Won in your CRM, spin up a shared onboarding group and bring the account team in.
Modules called
entergram_create_group_chatentergram_invite_chat_membersentergram_update_chat_info
The run produces
Group creation, invitations and a naming convention applied to the title and description, all from the webhook that fired when the deal closed. Onboarding starts the same hour the contract is signed instead of whenever someone gets round to it, and every client group ends up named the same way, which is worth more than it sounds when you have two hundred of them.
The scenario
Outside business hours, acknowledge inbound client messages and tell them when a human will pick it up.
Modules called
entergram_list_live_chatsentergram_set_message_reactionsentergram_send_message
The run produces
A time filter gates the whole branch, the reaction gives an instant visual acknowledgement, and the reply sets an expectation instead of leaving silence. Restrict the branch to conversations you have tagged as clients unless you want your friends receiving office-hours notices.
The scenario
On the first of each month, deliver the performance report to every retainer client as a document in their own chat.
Modules called
entergram_list_accountsentergram_list_chatsentergram_send_media_message
The run produces
The account module resolves which connected identity sends, the chat list narrows to the retainer conversations, and the media module attaches the PDF your reporting scenario generated upstream. Twenty client reports go out in one run and the history log proves each delivery, which is a better answer than searching your own outbox when a client says they never received it.
