Customer support agents

Govern customer support agents before they bind the company.

Refund flows, account resets, retention offers, policy explanations. Every message your support agent sends speaks for the company. Faramesh checks each action against policy before the customer hears back.

Tools we cover

One layer. Every support agent.

Faramesh hooks into the layer each agent runtime executes through. Zendesk, Intercom, Salesforce Service Cloud, your help desk, they all sit downstream of the framework. Govern at the framework, govern every conversation.

LangChain
LangChain
Auto-patches every tool call
LangGraph
LangGraph
Wraps the graph runtime
CrewAI
CrewAI
Governs every crew action
OpenAI
OpenAI Agents SDK
Hooks into Runner before tool execution
Claude
Claude Agents SDK
Intercepts tool calls before execution
Custom Python agents
One command, zero code changes
What's at stake

Support agents speak for the company.

Refunds, account changes, policy commitments. Every action carries legal weight under apparent authority. The risk isn't bad customer experience. It's promises and access changes the company can't undo.

Attack path · representative scenario5 minutes to account takeover
Routine task
Agent receives a 'my account was hacked' support request.
Reads context
Customer claims unauthorized purchases, wants credentials reset.
Decides resolution
Agent has tools for refund, password reset, and credential reissue.
Resets credentials
New auth tokens sent to the email the customer provided.
Customer was the attacker
Real owner locked out. Refunds wired to the attacker's card.
Every step looked rational. Faramesh would have stopped step 4 before credentials reset.
Other support agent risks
Binding promises
Air Canada doctrine. What your agent says is what your company owes.
PII leakage across cases
Agent shares one customer's data while resolving another's ticket.
Wiretap and disclosure exposure
Every recorded call is $5K per violation under CIPA. Disclosures must satisfy state law.
Recent signalsCalifornia SB 243 in effectJan 2026Chatbot wiretap suits surgeFeb 2026Air Canada apparent authorityJun 2025
Keep exploring

Other ways teams use Faramesh.

Use case

Payment agents

Govern refund agents, dispute bots, and AI commerce flows before money moves.

Use case

Multi-agent systems

Stop authority drift across orchestrators, planners, and executor agents.

Use case

Coding agents

Govern Cursor, Claude Code, Copilot, and custom coding agents before they touch production.

What changes when Faramesh is in front
Speak with authority you can defend.
Every refund, account change, and policy commitment runs through policy first. What your agent says is what your company is prepared to honor.
Pass every wiretap and disclosure audit.
Full conversation logs with policy decisions and reasoning. CIPA, SB 243, and state two-party-consent statutes all map to evidence you already have.
Stay ahead of state chatbot laws.
78 chatbot bills are moving across 27 states. Faramesh enforces disclosure, escalation, and content boundaries from a single policy layer that updates as the laws do.

Ship governed support agents.

Early accessView on GitHub