Cintesa Guide
Cintesa is a conversational site. Visitors ask and get an answer as generative UI. Content, Funnels, and the next step live in one project.
Last updated on
This is the public operator guide for Cintesa. It is the complete platform overview: what Cintesa is, how a project works, and how to set one up. Owners and Admins (and anyone with the link) can read it without signing in.
What Cintesa is
Cintesa is a conversational site for many unrelated projects. Each project is one visitor-facing site plus its own agent. Visitors land on a branded page — a hero and the content sections you publish — and can ask. The answer arrives as generative UI from this project’s published Agent Instructions and the pages and files you add: a section you published, or a block composed from this project. The same project can explain, qualify, convert, and keep the visitor.
You can run a project as the full customer-facing site, or as an embed on a brand site you already host. The model is organization → project. An organization holds billing, members, and one or more sites. Persona, facts, and conversion posture stay in that project. Cintesa does not apply one script, catalog, or journey to every customer.
The problem it solves
A conventional site shows the same pages to every visitor. Visitors come from different backgrounds and are at different stages of their journey. They scan the same pages, search for what applies, and many leave without an answer. Teams often add a chatbot beside the site, plus a separate form and a separate CRM.
Cintesa keeps that work in one project. Each visitor asks, and gets that answer as generative UI. A visitor can book a meeting, submit a form, or connect to a live person. Funnels decide when. Some brands keep their site and embed Cintesa. Others use Cintesa as the public site. Curated sections remain, for the page everyone can read before they ask.
Where it fits, one project can hold:
- The website — a branded landing with a hero, content sections, visual identity, languages, and SEO.
- The agent — answers from published instructions and ingested content for this project only, as branded generative UI.
- Funnels and conversion — Funnels and traffic rules unfold the right topics in order. Contacts and forms, conversation logs, scheduling, CRM, Agent tools, and Slack live chat carry the visitor to a meeting, a form, or a live person when the plan includes them.
- Agent readiness — public
llms.txt,agents.txt, andai.txtso a visiting agent gets faster discovery and instructions, rather than scanning the whole site. See Agent readiness.
What you get
- A visitor-facing site with a Landing Hero, content sections, and conversation.
- Agent Instructions you write and publish, plus answers from your content.
- Agent readiness — public files so a visiting agent gets instructions instead of scanning the whole site.
- Sources — website pages and files the agent can use.
- Funnels and traffic rules for campaigns and landing paths.
- Visual & UI, Atmosphere, and languages and SEO.
- Conversion tools: contacts and forms, conversation logs, scheduling, CRM, Agent tools, and Slack live chat.
- Delivery: domain, embed, and badge.
- Team, Client Sharing, Support, and plans.
Feature availability follows the organization plan. How-to pages that describe a paid capability start with Plan-related feature.
Stack
| Part | Role |
|---|---|
| Dashboard and visitor site | The Cintesa app — project settings and the live conversational site |
| Content ingest | Website pages and files you add so answers can use that content |
| Data | Hosted project data — settings, contacts, bookings, and logs |
| Agent | A hosted model, using your published Agent Instructions plus ingested content |
| Agent readiness | Public llms.txt, agents.txt, and ai.txt so a visiting agent gets instructions instead of scanning the whole site |
| Hosting | The app, visitor site, and this guide are hosted for you |
The platform provides shared mechanics (rendering, ingest, billing, delivery). Conversation behavior stays in that project’s published Agent Instructions and content.
Who is this for
- Owners and Admins setting up branded journeys and running a Cintesa project.
- In-house marketers who configure Funnels and need one next action until the site can go live.
- Agencies that run several client projects and may use Client Sharing.
- Prospects evaluating Cintesa — this guide is public; you do not need an account to read it.
This guide is not the visitor conversation, and it is not the engineering tree used to build the platform. When you are ready to work, sign in from the header.
Start here
- Get started — create an organization and project, follow setup guidance, then complete the five-step workflow.
- Build the site — General, Sources, Visual & UI, Content & Funnels, UI blocks, traffic rules, Atmosphere, languages and SEO.
- The agent — publish Agent Instructions, prepare Agent readiness, and preview how answers use your content.
- Convert — contacts, conversation logs, scheduling (including team assignment), CRM, Agent tools, Slack live chat.
- Operate — project management, activity and usage logs, visitor personal data, notifications.
- Deliver — domain, embed, badge.
- Roadmap — planned work. Changelog — released functionality, functional changes, and resolved issues.
- Team & billing — members, Client Sharing, Support, plans.
Need a limit or a stuck save? See Reference.
© 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.