Message templates save frequently used text, variables, and attachments as reusable replies. The storage page shows the workspace capacity used by these platform files, ticket files, and broadcast files.
Create a message template
Open Settings → Message templates. Enter a name, body, visibility, and optional shortcut. Upload attachments and adjust their order if needed, then save. The template becomes available in the chat composer.
| Visibility | Who can use it | Who can edit it |
|---|---|---|
| Personal | The creator | The creator |
| Shared | Members of the current workspace who meet the access requirements | The creator; administrators cannot edit someone else's template solely because it is shared |
Sharing allows members to read the content. Check that the text and attachments are appropriate for the team before making a template shared. Changing it back to personal removes other members' future access but cannot recall content they have already seen or sent.
Saving content changes creates a new version. Editing text after inserting it into a chat does not change the original template. Submitted broadcasts use independent content snapshots and do not change when the source template is edited later.
Insert a template in chat
Use the template entry in the composer to search by name or shortcut, or type a shortcut such as /greet at a word boundary and select a suggestion.
The default action inserts content into the draft for review before sending. Send directly is a separate action that actually sends the message. Attachments are added to the pending attachment area.
Save shortcuts without /, using only English letters, numbers, and underscores. Matching is lowercase. Shared shortcuts are unique within a workspace; personal shortcuts are unique for that person in the current workspace. A personal and a shared template may have the same shortcut, so check which suggestion you select.
This is a TgSpark editor shortcut. It does not register a Telegram Bot command or change typing behavior in the mobile Telegram app.
Use variables
| Syntax | Meaning when inserted into chat |
|---|---|
{{客户}} |
The current chat contact's display name |
{{我}} |
The current agent's display name |
{{账号}} |
The sending Telegram account's display name |
{{日期}} |
Today's date in the workspace time zone |
These variable names are literal product syntax and remain in Chinese. For example, save Hello, {{客户}}. I'm {{我}}. and check the substitutions after insertion before sending. Unknown variables remain in the text and trigger a notice. Business variables such as order numbers are not fetched automatically from your business system; fill them in manually.
Manual chats replace variables when a template is inserted. Broadcasts generate content for each recipient on the server. Check recipient previews before submitting a broadcast.
Attachments and capacity
Common current platform limits are 10 MiB per file and up to 10 files totaling 50 MiB per template. The backend validates file types and module-specific limits; the template page reads these limits from the server.
Settings → Billing and storage shows the total quota, used capacity, upload reservations, available capacity, category usage, and accessible file details. New workspaces receive the quota configured for the deployment; 5 GiB is an example. Changing the default does not retroactively change existing workspace quotas.
| Usage label | Meaning |
|---|---|
| Used | Platform files that have been saved and not yet released |
| Upload reservation | Capacity reserved for unfinished uploads to prevent concurrent uploads from exceeding the quota |
| Pending release or cleanup | Cleanup has been scheduled; capacity is released only after physical deletion succeeds |
| Available | Total quota minus used capacity and upload reservations |
Uploading the same file again creates another asset counted separately. Copying template attachments into a broadcast also uses additional storage. Seeing total usage does not grant access to someone else's personal template files; business permissions still govern file access.
Cleanup and common questions
Before deleting a file, check whether template versions, broadcast snapshots, or tickets still reference it. The file list cannot bypass these relationships to delete referenced files. If deletion shows a pending release, wait for background cleanup; capacity may not change immediately.
| Question | What to do |
|---|---|
| A template is missing from search | Check the workspace, visibility, enabled status, and search terms |
| A shortcut conflicts | Change duplicates within the same scope; matching is case-insensitive |
| A shared template can be used but not edited | Only its creator can edit it; contact the creator |
| Upload fails | Check type, individual and total sizes, and available workspace capacity; operations should check directory and proxy limits |
| Deletion did not restore space | Check references and cleanup status; operations should investigate cleanup errors if release remains stuck |
| You want to top up, pay, or change plans | The current page provides usage information; automatic billing and charging are not implemented |
Implementation references: message templates, storage usage, template API, and file API.