How you work with Parahelp
You do all of this in tasks. It starts with an onboarding task, where the Internal Agent analyzes your historical resolved tickets and existing documented context to build the first version of your Customer Agent. From there, the two agents run a continuous improvement loop, and every turn of it starts with a gap:- Identify gaps (Internal Agent). When context changes - a merged PR, an updated page in Notion - it prompts the Internal Agent to investigate using its broader connections. The same happens when the Customer Agent lacks context on a ticket. See Identify gaps.
- Build (Internal Agent). The Internal Agent builds the scoped policies, knowledge, and tool connections from the gap it identified, and asks you in natural language when it needs input. See Build.
- Test (Internal Agent). The Internal Agent tests the change against your historical support tickets, and production tests verify your tool connections. See Test.
- Resolve (Customer Agent). Once your team approves the release, the Customer Agent uses the updated configurations to resolve tickets end-to-end across your channels - email, live chat, and Slack. See Customer Agent.