Claude & ChatGPT

Connect Claude Code, Codex, Claude or ChatGPT to Rose, then work on your agent and read what happened on your website by chatting with your assistant. Next to your CRM, Slack or enrichment connectors in the same assistant, Rose brings what visitors asked and which companies are in market; the other tools act on it.

What your assistant can do

Improve your agent's knowledge

• Read, add, edit and delete the FAQs and documents your agent answers from.
• Preview changes for your confirmation, then save them, retrain your agent and ask it the question again to check the new answer.

Report what happened on your website

• Give your conversation totals for a period: conversations, emails captured, demos proposed and booked, call-to-action clicks.
• List every topic visitors raised, with questions they typed in their own words, the most frequent keywords, the pages they chatted from and the companies Rose identified.
• Export the conversations themselves, with their topics, keywords, outcomes, company and transcript, for all of them or only those on a topic or keyword.
• Compare a period with the one just before: totals, how often each topic came up, and the topics visitors stopped raising.
• List the companies whose visitors chatted with Rose, highest intent first, with the intent score of your Accounts page: a call list your assistant can pass to your CRM.
• Report Rose's impact over the last 7, 14, 30 or 90 days, as the Rose impact tab of your analytics: conversions of visitors who chatted against those who did not, and Rose-assisted conversions per month.

Report a problem

Ask your assistant to report a specific Rose answer or a general problem. For an answer, it reads the conversation, identifies the assistant message, and asks what should have been said if that is unclear. The report includes the visitor's question, Rose's answer, your expected answer and a link to the conversation.

For either report type, explicitly select the affected workspace. Check the workspace, your signed-in email and the full report in the preview before you confirm submission. The resulting ticket appears in Support in your backoffice. See Reporting a problem.

Connect your assistant

1. In the Rose backoffice, open Integrations > AI assistants and select Claude & ChatGPT.
2. Copy the Connection prompt and paste it into Claude Code, Codex, Claude or ChatGPT.
3. Follow your assistant's setup guidance. Claude Code and Codex can register the server with their own commands. In Claude or ChatGPT, you may need to add the Connector URL from the same panel yourself:
   • Claude: Customize → Connectors → Add custom connector, then paste the URL.
   • ChatGPT: Plugins → Add custom MCP server, then paste the URL and enable the resulting plugin in your chat.
4. Sign in with your Rose account and allow the connection.
5. If your assistant needs a restart or a new chat to load the tools, follow its guidance to resume. Ask it to list your Rose workspaces to verify the connection.

If Rose is already connected, the prompt reuses that connection. Your assistant may need your workspace administrator to allow custom connectors before you can add one.

Your assistant gets the same access as your own sign-in: it sees the websites and data you see in the backoffice. To disconnect it, remove the connector in your assistant's settings.

Confirm changes in your assistant

The Rose connector instructs your assistant to:

1. Preview the change without saving it.
2. Show you the before/after diff and ask you to confirm that exact change.
3. Apply the change after your confirmation. Knowledge changes retrain your agent; support tickets return a ticket number and link.

Confirmation is handled by your assistant and its tool-approval settings. Rose checks that the change comes from an unexpired preview made by your account, but does not independently check what your assistant showed you or whether you approved it. There is no separate approval step in the Rose backoffice. Review the diff before you confirm a change in your assistant.

Use it with your other tools

Rose does not write to your CRM or send messages itself. Add the connectors of the tools you use (HubSpot, Salesforce, Slack, Clay…) to the same assistant, and ask for the whole task in one message:

• "List this week's hottest accounts from Rose and add them to the HubSpot list 'Rose — in market'."
• "Prepare my call with Acme: what did their visitors ask Rose this month?"
• "Post to #marketing what changed in visitors' questions this week compared with last week."

The other connector decides what it can do; check its permissions before you let your assistant write there.

Try it

• "What did visitors ask on our website this month? Group it by topic."
• "Which companies chatted with Rose last week, and about what?"
• "What changed in what visitors asked this month compared with last month?"
• "List our 20 hottest accounts this month and add them to a HubSpot list."
• "How did visitors who chatted with Rose convert over the last 90 days?"
• "Export last month's conversations about pricing, with their transcripts."
• "Find the conversations that mention payslips and summarize the objections."
• "Our FAQ on pricing is outdated: show me the change, then retest the question."

The tools your assistant uses

Your assistant shows these names when it calls Rose, and may ask you to approve each call. Only apply_change saves changes or submits support tickets: approve it after you have seen the preview's diff.

Every tool except list_workspaces and apply_change also takes a workspace_id, one of the websites list_workspaces returns. Dates are YYYY-MM-DD; a period is 92 days at most, and until defaults to today.

Tool	Parameters	What it does
list_workspaces	none	Lists the websites your account can work on.
read_conversation	conversation_id from export_conversations, or session_id from a backoffice conversation link	Reads messages and their ids so you can identify the exact answer to report.
preview_chatbot_issue	conversation_id; message_id from read_conversation; issue_subtype: not_accurate or accurate_but_not_ok; expected_answer	Prepares the same conversation report as the backoffice, using the stored visitor question and Rose answer.
preview_support_issue	title; description	Prepares a generic support ticket without a conversation.
list_faqs	search (optional): words to find in questions and answers	Reads your agent's FAQs.
list_documents	none	Lists the documents you uploaded (not your website's pages).
read_document	document_id	Reads one document's text.
preview_faq	faq_id to edit an FAQ, none to add one; question and answer (required to add); topic; enabled (false hides it without deleting it)	Shows the FAQ change as a before/after, without saving it. Fields you leave out keep their value.
preview_faq_delete	faq_id	Shows the deletion, without deleting.
preview_document	name; markdown, the full new text; document_id to replace a document, none to add one	Shows the document change, without saving it.
preview_document_delete	document_id	Shows the deletion, without deleting.
apply_change	change_token, from a preview	Saves a knowledge change and retrains your agent, or submits the previewed support ticket and returns its number and link. Your assistant must obtain your confirmation first.
retrain_status	operation_id (optional, from apply_change); without it, the retrains still running	Says whether the retrain has finished.
ask_agent	question; change_token (optional, from preview_faq) to answer as if that FAQ change were saved	Asks your agent a question, as a Playground test: it counts in neither your analytics nor your plan usage.
conversation_overview	since, until; compare_previous (default false)	Totals, topics with visitors' questions, keywords, pages and companies for a period; with compare_previous, the same number of days just before too.
export_conversations	since, until; topics, keywords (optional filters); include_contacts (default false); include_transcripts (default true); offset, limit (50 per page, 100 at most)	The conversations themselves, page by page.
list_accounts	since, until; limit (default 20, 50 at most)	The companies whose visitors chatted with Rose, highest intent first.
impact_report	days: 7, 14, 30 (default) or 90, ending now	The Rose impact numbers for that period.

What the conversation reports include

• Live conversations only: the same conversations as the backoffice's default view. Playground tests and test environments are left out, and so is your own team's traffic, as in your backoffice statistics: your own company, and the internal IP addresses you set in your analytics settings.
• Up to 92 days per request: for a longer period, ask for it in several parts.
• Impact is an observation, not an A/B test: visitors who chat may already be more likely to convert, so the gap between the two groups is not Rose's effect on its own.
• Accounts and impact cover the whole website. If your website is split into several workspaces by path, these two reports include all of them.
• Keywords are in English, whatever the conversation's language. A keyword search ignores case and also finds longer forms: "payslip" finds "payslips".
• Visitor names and emails only when you ask for them. By default, a report stops at the visitor's company. Transcripts still show everything visitors typed, including an email they gave Rose in the chat.
• An empty report says why. For example, with no conversation in the period, it asks you to check that the widget is installed and shown to visitors. Companies appear once Rose identifies them: see prospect qualification.

If something goes wrong

• "Rose staff accounts cannot use this connector": sign in with your own client account.
• "No workspace … for this account": your account has no access to that website. Ask your assistant to call list_workspaces, or ask whoever manages your Rose account for access.
• A new FAQ is not used yet: the retrain takes a few minutes; ask your assistant to check retrain_status, then ask the question again.
• What your assistant reads leaves Rose: answers, conversations and contacts go to your AI provider under your account's terms with them, like any document you share in a chat.