Bot messages
Word every message Synq's Telegram and Discord bots send about your communities in your brand's own voice, with fill-ins, a live preview and Synq's wording one tap away.
Every message Synq's bots send about your Telegram groups, Discord servers and roles can be in your brand's own words: each announced window's announcement and reminders, a Telegram group's or a Discord role's, the names of those still to verify, the closing message, every direct message about someone's place, Discord's Verify message and the replies its button gets. Synq's wording stays the default, and putting it back is one tap.
Synq's own wording is warm and plain, with at most one emoji, and fits any brand. It never assumes what your gate asks for: it says verified, never holders, and where it says what qualifies, that's your gate's own rule in a line ("To qualify: Used Acme Swap at least 3 times in the last 30 days."). It names your members with your brand's word for them, and members never have to message the bot.
Word them under Communities → Messages in the dashboard, each message in its own box with a live Telegram- or Discord-style preview, through the management API (list a brand's messages, read their frame, and change them), or with your agent: the MCP server's get_configuration reads them (community_messages, each message in short, with resource_id discord or telegram for one platform's and discord.not_met for one message in full; community_message_frame) and update_configuration changes them (update_community_messages). Both need org.integrations.view / .edit, and the words are the brand's, for all of its groups and servers.
$SYNQ_API here is the management API, https://api.synq.build, and $SYNQ_API_KEY an API key with org.integrations.edit:
curl -X PATCH "$SYNQ_API/v1/orgs/$ORG/brands/$BRAND/community-messages" \
-H "Authorization: Bearer $SYNQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"messages": {
"telegram": {
"reminder_d7": "**One week, {members}.** {verified_members} are in. Tap Verify and stay with us.",
"approved": "Welcome to **{group}**, {member}."
},
"discord": { "removed": "**@{role}** is gone for now: your wallets no longer qualify." }
}
}'Send null for a message, or Synq's own wording, to put Synq's back. What you leave out stays as it is.
What you write
- Plain words and line breaks.
**bold**is the only formatting. Anything else, a Telegram HTML tag or Discord markdown (#,-,[link](…),<@…>), shows as typed: Synq escapes it for the platform, so your words can't break a message or mention anyone. - Fill-ins, such as
{group}or{deadline}, are replaced as each message goes. Each message takes its own;GET …/community-messageslists them with an example each, in your brand's own names. Start one with a capital,{Members}, and its value starts with one. - What a message needs. A message about the deadline must name it with
{deadline}(the last reminder may say only{deadline_time}), the names message{names}, a grace message when the role or access ends ({ends}), and so on (required). - A length that fits. Each message has its own longest (
max_length), and with its longest fill-ins it must stay within the platform's limit (limit): Telegram's 4,096 characters, Discord's 2,000, or 4,096 in an embed.
Anything else is refused with 400 validation_failed, at the field, with what's wrong and the fix:
| Refused | What the API says |
|---|---|
| A fill-in the message lacks | {role} isn't a fill-in of this message, so Synq can't fill it in. Use {brand}, {group}, {button}, {members} or {member}, or plain words. |
| No deadline where it's needed | This message must say when the deadline is: add {deadline}. |
| A stray brace | A brace that isn't part of a fill-in: write the fill-in whole, such as {group}, or remove the brace. |
| Bold that never ends | Bold starts with ** but doesn't end: put ** after the bold words too, or remove it. |
| Too long | At most 1,000 characters: this one has 1,001. Shorten it., or how long its longest fill-ins could make it, and the limit |
- Counts read right. After a count of 1 (
{settled},{verified},{verified_members},{to_verify},{total}), the sentence's first have, are or were becomes has, is or was: "1 who didn't verify has left". In the closing message, a sentence whose count is 0 is left out: no "0 members verified: thank you". Synq's own words do the same. - Times read as members read them.
{deadline}is the moment on the group's clock, 12-hour, with the zone's short name (Dec 8, 6:00 PM ET; ET, never EST or EDT; UTC for a group that set none), and{deadline_time}its time of day (6:00 PM ET).{ends}and{until}say how soon first when it's within a week, then when, and go on a sentence by themselves, with no on or until before them:you'll be muted {ends}reads "you'll be muted in about an hour (Nov 9, 12:34 AM ET)" or "on Nov 20, 6:00 PM ET". On Discord, times show in each reader's own time zone.
Some fill-ins have no value at times (optional): a gate's rule too long to read in a line ({asks_for}), a group with no invite link ({invite_link}), a server with no Verify channel ({verify_channel}). A message of yours that uses one goes in Synq's words that time, never with a hole in it.
What you call your members
Your brand calls its members one thing, everywhere: in every message's {members} ({Members} with a capital) and {member}, in counts such as {verified_members} ("612 players", "1 player"), on your member profile and in the dashboard's counts. It's "members" and "member" until you set your own, at the top of Communities → Messages, or with members_called on the same PATCH:
curl -X PATCH "$SYNQ_API/v1/orgs/$ORG/brands/$BRAND/community-messages" \
-H "Authorization: Bearer $SYNQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "members_called": { "plural": "players" } }'Give the plural, and the singular where one final s off isn't it: players gives player on its own, and staff needs "singular": "staff". Each is at most 24 characters on one line. null puts Synq's words back. The frame reads them (members_called), and the MCP server's community_message_frame too.
What Synq keeps
Your words replace Synq's inside the same frame, which no text can take out:
- your brand's name above each Telegram message, and "Powered by Synq" under it where your plan shows it, as your hosted pages do; on Discord, the embed's look: your name, icon (or a square logo) and accent color. In the group, the name line is left out where the group's own name starts with it ("Acme Holders" for Acme): Telegram's chat list runs a message's lines together, and would read "Acme Acme Holders…"
- the window's headline above the announcement (Synq's, where the window has none of yours, is "🔐 Acme Community is for verified members from Dec 8, 6:00 PM ET.") and its countdown line under it ("⏳ 30 days left · 612 of 1,068 verified"), which Synq edits once a day
- every button: Verify with Synq, the personal link, Open my profile and Ask to join
- on Discord, anything a direct message couldn't tell someone, first in the answer to their next Verify press
What Synq says about Synq itself stays Synq's: a code that didn't work, a server that isn't connected, a slow-down. So does what it says when someone's account at your brand was deleted: your words about wallets wouldn't be true then, so Synq says the account was deleted and that verifying again starts fresh.
New words go from the next message sent. A Telegram window's pinned announcement takes them at its daily update, and Discord's Verify messages are redrawn in place when you save, which notifies nobody.
The Verify button
The button says Verify with Synq on Pro, since every tap advertises Synq. On Scale and Enterprise, the plans that may hide "Powered by Synq" and bring their own bot, you may name it with verify_button, {brand} its only fill-in:
{ "verify_button": "Verify with {brand}" }At most 40 characters, on one line. Synq's own words name it as it reads ("tap Verify with Acme below"), and so does {button}. Naming it on another plan is 403 plan_feature_unavailable; after a move down, the button says Synq's again and your text is kept for when you move back.
Each change is recorded as brand.updated, with community_messages.<platform>.<message> or community_messages.verify_button from and to.
Member profile
The page your community's members land on after Verify with Synq or a Telegram join request, in your brand's look, with their wallets, gates and communities.
Logos, icons and backgrounds
Upload a brand's logo, its icon and its sign-in background straight to Synq's storage, then finish the upload.