Let agents do the work in your systems.
With a person on the risky steps.
Agents look things up and take action in the systems you already run: your own code, a vendor's API or a server inside your network. You decide which actions wait for a person, and every action is recorded in the run.
What the agent can finish with the right tools.
Four jobs at a telecom provider. Each mixes tools you write, tools connic ships and a rule for when a person steps in.
The agent fills in the port request on the old carrier's web portal and files the confirmation PDF. When the portal asks for a sign-in code, it asks the porting team and waits.
Technicians tell the assistant what they did on site. It closes the job and orders parts as that technician, after they connect their account once.
Uses
- MCP server
- Per-user sign-in
- Field-service tools
After a repair, the agent schedules another run for 8:00 the next day. That run checks the line and texts the customer the result.
Uses
- Scheduled run
- Line check
- Twilio Messaging connector
When a company signs up for business lines, the agent reads its website and recent news. It writes a short profile into the CRM, with a link to every source.
Uses
- Web search
- CRM update
- Webhook connector
Reach every system the work touches, even behind your firewall.
Your billing API, the field-service platform and the network management system stay where they are. Each becomes a set of tools your agents can call.
line-supportcan call- Billing systemYour own APIFunction in code
billing.* - Field-service platformVendor API with an OpenAPI specOpenAPI spec
api:field_service.* - Network managementInside your networkMCP server through a bridge
bridge: ${NOC_BRIDGE_ID}
field-assistantcan call- Technician accountsOne sign-in per technicianMCP with per-user sign-in
credential: fieldops
- No inbound ports
- A bridge connects out from your network, so internal systems stay private.
- Each person acts as themselves
- Each employee connects their account once, and the agent acts with that person's access.
- Search, files and the web come built in
- Built-in tools search your documents, read and write records, use websites and hand work to other agents, with no code to write.
Small credits go out at once. Bigger ones wait for a team lead.
You decide which tools the agent sees for which caller, which actions wait for a person and what is stopped outright.
- Some tools only for verified callers
- The agent can only cancel a contract after the caller has been verified.
- A person approves above your limit
- Credits up to €25 go out at once. Bigger ones pause the run until a team lead decides.
- Hard stops for what must never happen
- Your own code sees every action before it runs and can change it, hide parts of the result or block it.
One file decides what the support agent may do.
The agent behind the support chat at the top of this page, with every tool source and the rule for credits.
version: "1.0"
name: line-support
description: "Fixes connection problems in the support chat"
model: connic/gpt-5.6-terra
system_prompt: |
Help customers with connection problems.
Check the line before you book a technician.
tools:
- billing.lookup_invoice
- billing.issue_credit
- billing.cancel_contract: context.customer_verified
- api:field_service.appointments_create
- trigger_agent_at
mcp_servers:
- name: network
url: http://nms.internal:8080/mcp
bridge: ${NOC_BRIDGE_ID}
tools:
- line_status
- outages_near
approval:
tools:
- billing.issue_credit: param.amount > 25
timeout: 3600
on_rejection: continuebilling.lookup_invoiceFunctions in your code
billing.lookup_invoiceis a function intools/billing.py. Its type hints and docstring become the tool's schema.billing.cancel_contract: context.customer_verifiedConditions
The model only gets
cancel_contractwhencontext.customer_verifiedis true.api:field_service.appointments_createOpenAPI spec
Every endpoint of the field-service API becomes a tool. connic adds the credentials to each request.
bridge: ${NOC_BRIDGE_ID}MCP server in your network
The network management system's MCP server stays private. The
bridgeconnects out, so it needs no inbound ports.billing.issue_credit: param.amount > 25Approval above €25
Bigger credits pause the run until a team lead decides. With
on_rejection: continue, the agent tells the customer instead of failing.