Skip to main content
Common questions and fixes. When in doubt, ask the Internal Agent: it can investigate a ticket, explain a behavior, update a configuration, or connect a new tool for you. Start a task at app.parahelp.com.

Customer Agent

Prompt the Internal Agent. Describe what you want to change, like a refund policy or a new tool, and it will draft the update, test it, and stage it for your approval. See Build.
Ask the Internal Agent to run test simulations. It generates realistic test cases, runs them in a sandbox, and reports back with the agent’s reasoning, tool calls, and final reply, so you can iterate before publishing. See Test.
Ask the Internal Agent to QA the ticket. It will identify the knowledge or instructions that led to the behavior and suggest a configuration fix if needed.
Ask the Internal Agent to investigate the ticket. It can read what happened, explain it, and propose a fix. You can also set a Slack channel for tool error notifications in Settings.

Platform

Finishing a task ends the session. Changes go live only when you approve the pending action. If an action is still pending, it hasn’t been published yet. See Release.
For managed connections (Linear, GitHub, Notion, Cursor, Slack), connect in one click on the Connections page in Settings. For anything else, prompt the Internal Agent to wire up an MCP server or API endpoint. See Connections.
Add them under Members in Settings and assign Admin or Operator. Admins can approve and publish actions, and operators can draft and propose.
Start a new task whenever you move to a new topic. The Internal Agent works best when it isn’t holding unrelated context. See Tasks.
No. Context is self-managing, with auto-compaction built in, so long conversations stay accurate. Just start a new task when the topic changes.
Someone on your team published a change to the same file after you drafted yours. Click Fix it under the Actions tab, and the Internal Agent will resolve the merge conflict for you. Publishing releases as soon as they’re ready avoids this. See Release.
Tools built before Parahelp 3.0 are managed by us and marked as legacy. Ask the Internal Agent to rebuild one as a new tool, and you’ll be able to view and edit it yourself. The Internal Agent’s own configurations are also managed by us for now.

Ticketing systems

Intercom, Zendesk, Front, Plain, and Pylon, one per workspace. See Ticketing system.
You set up a workflow in your ticketing system that assigns tickets to Parahelp, so you control exactly which tickets it handles. See Ticketing system.

Security and privacy

Yes. Parahelp does not store PII by default. Manage data retention in the Privacy section of Settings, or see our trust page.
No. Every proposed change waits as an action until an admin approves it, unless you have explicitly set that action to auto-approve. You can additionally require Slack approval for specific Customer Agent actions, like refunds. See Release.
Yes, Parahelp is SOC 2 Type II and GDPR compliant, with encryption in transit and at rest.