Agent Instructions
Write, save, and publish Cintesa Agent Instructions, including @ references to sections, UI blocks, tools, media, and links.
Last updated on
Open Agent Instructions. This is workflow step 5.
Write and save
- Describe how the agent should greet, what it may promise, and when to offer a form, booking, or human handoff. Authoring actions has two tabs: Generate a full draft (from this project’s setup and ingested sources) and Add sections one by one (insert one of the same five blocks). Read the draft and edit it before you save. Generate does not publish by itself. Both actions write the same five labeled blocks: role and persona, hard constraints, reply structure, a map of this project’s saved sections and enabled UI blocks, and boundaries. Generate writes all five at once. Add sections one by one inserts the block you pick at the cursor.
- Save creates the first version automatically. When the draft has unsaved changes, the save bar includes Publish this version after saving. It starts unchecked. On that first save, and on Save as new version, leave it off to keep an unpublished version and publish later from version history. Check it to save and publish in one step. One saved version moves the workflow; Publish completes the step and is what visitors get. Later edits can Save in place (that save does not publish) or Save as new version. Publishing an older version from version history still works.
Keep the document under 15,000 characters. The editor shows how many characters you have used. A longer draft cannot save. If save fails for length, shorten the text and try again.
Unpublished drafts do not change the live site.
The Messages tab holds fallback, handoff, input disclaimer, and returning-visitor copy. When the project has another language, each message section shows a tab for each language. The default language is the source. Select a language, then Generate translations. A language you just added starts on Generate translations. Review the fields, then Save messages. The live page uses that language’s messages after the save. After a translation exists, the button is Regenerate translations. It replaces only the selected language. If that language is already on the live page, the replacement is saved immediately. Changing Enable returning visitor experience shows Save messages.
Plan-related feature. Generate draft (AI instructions), Generate translations, and Regenerate translations are available on Pro or higher (AI content generation). You can still edit each language by hand on every plan. On Basic and Starter the same five blocks are filled from project setup, and the dashboard shows an upgrade notice. Instruction insights (suggestions from recent conversation logs) is available on Agency or higher. See Plans.
What belongs here
Persona, reply shape, pricing you want stated, demo links, and any intent-specific answers belong in these instructions (and in ingested pages). Do not expect the platform to hardcode a tenant’s product story.
Visitor prose is formatted for you. Paragraphs are separated, lists and emphasis are used when they fit, links are written as link text, and a longer answer uses headings. You do not add those formatting rules here. If you publish different prose formatting, that published text is what visitors get. What a reply looks like is on Reply expectations.
Shape of a reply
You choose the order. A full answer can be these four parts, and you can leave a part out when that turn does not need it:
- Opening text.
- A Content Section you already saved, or a section composed for this turn.
- One follow-up question.
- Suggested next-step buttons.
When the reply ends with a follow-up question, visitors get a button that sends the choice that question offers. Only a reply that asks a follow-up question includes that button. You can leave the question out when the turn does not need one.
Point at a saved section with @page_section:<tag>. Point at a library shape, including opening text (@ui-block:free_text) and suggested next steps (@ui-block:cta_buttons), with @ui-block:<id>. Generate a full draft and the Reply structure block include a default order: opening text (@ui-block:free_text), one relevant section or UI block, then next-step buttons (@ui-block:cta_buttons). Edit or remove any part before you save. Map and triggers lists only this project’s saved sections, enabled UI blocks, and media tags.
The agent reads the published instructions and this project’s content first, then sends the whole answer as one reply. Visitors see one response, not a reply built one piece at a time. Another project can publish a different order. The platform does not force this shape. How many parts a reply can show, the monthly includes, and what visitors see when a reply stops are on Reply expectations.
Platform references
The editor can link a sentence to a real platform object. Type @ and pick from the project’s published sections, media, UI blocks, and tools. You can also paste a full https:// link. The footer under the editor is the color legend for those tokens.
Use references when you want the agent to show a specific Content Section, compose a specific UI-block shape, attach a library image, or call a connected tool. Pick from the menu so the spelling matches the published object. Do not invent tags.
How to insert a reference
- Click in the instructions editor.
- Type
@. A menu opens, grouped as Sections, Media, UI blocks, and Platform tools. - Filter by typing a name or tag, then choose the row. The editor inserts the exact token.
- For a public URL, paste the full
https://address. The editor highlights it as a link. - After you insert a section token, confirm the tag against Content & Funnels → Content sections. The published tag is the source of truth.
The menu only lists objects this project already has. A section appears after you save it. Media appears after you upload or ingest it. Connected tools appear when that integration is on.
Do not leave raw tokens in anything the visitor should read. Visitors see the rendered section, block, or image — not @page_section:….
Color codes
Each kind of reference uses one color in the editor. The same colors appear in the footer legend.
| Kind | What it marks |
|---|---|
| Link | A full http:// or https:// URL |
| Media | @asset_… brand files and @page_media_… ingested page media |
| Section | @page_section:<tag> (the picker). @section:<tag> also highlights |
| UI block | @ui-block:<id> and the matching block name |
| Platform tool | A connected tool the @ menu inserts |
| Placeholder | A template field such as {{businessName}} |
Name convention
Write tokens exactly. The picker inserts the legal form. Hand-typed tokens must match the same pattern or they stay plain text.
| Kind | Write it as | Allowed characters | Example |
|---|---|---|---|
| Section | @page_section:<tag> | Tag: lowercase letters, numbers, and hyphens; 1–50 characters. No capitals, spaces, or underscores | @page_section:works-gallery |
| Section (legacy highlight) | @section:<tag> | Same tag rules. Prefer @page_section: from the menu | @section:welcome |
| Brand media | @asset_<slug> | After the prefix: lowercase letters, numbers, and underscores; 1–48 characters | @asset_logo |
| Page media | @page_media_<slug> | Same slug rules as brand media | @page_media_hero |
| UI block | @ui-block:<id> | Catalog id in snake_case (lowercase letters, numbers, underscores) | @ui-block:lead_capture_form |
| Platform tool | The name the @ menu inserts | Use the picker so the spelling matches | Slack live chat, calendar, HubSpot — when connected |
| Link | Full URL | Must start with http:// or https:// | https://www.example.com/pricing |
| Placeholder | {{camelCaseKey}} | Letters only inside the braces | {{businessName}} |
Section tags come from Content & Funnels. If the section is Works gallery with tag works-gallery, the token is @page_section:works-gallery — not @page_section:Works_Gallery.
Media tags come from the brand library or ingested page media. Do not invent a slug. Do not paste image URLs when a tag exists; tell the agent to use that tag on the image field.
UI-block ids are the library names, for example @ui-block:free_text, @ui-block:cta_buttons, @ui-block:lead_capture_form, @ui-block:appointment_scheduler, @ui-block:pricing_table. Type @ and pick the block instead of guessing. The full catalog and when to use a saved section instead is on UI blocks.
Name a platform action when this project has that capability. Type @ and pick the tool from Platform tools instead of guessing a name:
- Compose a library UI block
- Slack (when connected): start live chat, or request approval
- Calendar (when connected): create an event
- HubSpot (when connected): find a contact, get contact context, log a note, or update a deal stage
Connect tools on Agent tools. Instructions decide when to call them. The platform does not invent a handoff, booking, or CRM action from a keyword.
Placeholders appear in Add sections one by one templates. Fill company name, domain, and similar fields under General, or replace the {{…}} text yourself before you publish.
When to use each kind
| Use | Token | Result |
|---|---|---|
| Show a package you already designed | @page_section:<tag> | Renders that Content Section exactly as saved |
| Compose a library shape from this project’s content | @ui-block:<id> | Builds that block and fills it from instructions and ingested content |
| Attach a library image | @asset_… or @page_media_… | Use the tag on the image field — do not invent a URL |
| Name a platform action | Tool name | The agent may call that tool when your instructions say to |
| Share a public page | https://… | A highlighted link the agent can offer |
Choose @page_section: when the layout and copy already live in Content & Funnels (a gallery, a bio, a survey, a booking section). Choose @ui-block: when you want that shape filled for this turn. Do not mix a made-up section tag with a UI-block id.
After publish
Change copy, save a new version, and publish again. Preview after each publish — see Preview.
© 2026 Cintesa. Guide text and screenshots are Cintesa product materials for personal and operator use. Do not scrape or republish them commercially without permission. Terms of Service · Privacy Policy.
The agent
Publish Cintesa Agent Instructions, prepare Agent readiness, and preview how answers use your content.
Reply expectations
What one visitor reply includes, the token spend and time to expect, monthly conversation includes, and what people see when a free-text reply cannot finish. Saved Funnels keep working.