Back to Solutions
Customer support

Resolve the issue.Respect the boundary.

Give support assistants the tool access they need to investigate a ticket. Keep sensitive fields and consequential actions behind explicit rules.

See a support workflow
The useful context

A complete answer doesn’t need a complete account.

Configure which tools and records an agent can request. Apply field redaction before permitted results return to the assistant.

Ticket 6824Replacement hasn’t arrivedAssigned · Jo
Customer message
“The replacement was meant to arrive yesterday. Can you check where it is?”
Resolution context

Order status and tracking are relevant. Payment details are not needed for this answer.

Returned to the assistant

Order
R-2086
Carrier status
Delayed · new delivery Friday
Replacement
Already dispatched
Payment card numberREDACTED
Internal fraud notesNOT REQUESTED
Illustrative support case · access and redaction require configuration in Fabriq.
Separate preparation from permission

Ready to reply.
Still yours to send.

A helpful draft and permission to contact a customer are different things. Give the assistant a narrow toolset; require approval for configured send actions.

Draft responseCustomer-facing

Your replacement is on its way. The carrier has updated the delivery date to Friday.

I’ve included the tracking reference so you can follow its progress.

Draft preparedSend requires review
Read shipment statusGranted tool access
Return account detailsSensitive fields filtered
Send externallyApproval policy applies
When the case needs a person

Make the exception
easy to pick up.

When a configured policy holds a tool call, keep the request and its decision visible. Your support team handles the customer conversation in its existing helpdesk.

Supervisor handoffCase 6824
Requested action
Send replacement confirmation
Agent / acting user
delivery-helper / Jo
Policy outcome
Approval required
Provider execution
Not sent while held

A tool-call record gives the reviewer the request and outcome—not the model’s private reasoning.

Put useful assistance
inside clear support limits.

Discuss your support stack