Agents do the routine work.
People approve the risky step.
Hold payments, refunds or record changes for a person's approval. The run waits with the exact details and carries on once someone approves in connic, in your own app or by API.
Agents that know when to wait for a person.
The agent does the work up to the risky step and waits there. Once someone decides, it finishes the job.
A traveler emails to move a group trip. The agent finds new flights and holds the €1,240.00 change fee until a team lead approves, then confirms by email.
An airline portal sends a one-time code to the agency's phone. The agent asks for it in the agency's own trip desk app, and a team lead types it into a masked field.
A traveler asks for a refund on a non-refundable stay. The reviewer rejects it with a reason, and the agent offers a free date change instead.
Your team decides where it already works.
Each request shows the agent, the action and its exact details. Decide in connic, in a review screen you build, or from your own systems.
- Clear rules on who decides
- Permission groups set who can see and decide requests in connic.
- Your own review screen
- On developer, pro and enterprise, an app you host on connic can list and decide requests, and connic records who decided.
After the decision, the run carries on from where it paused.
Nothing that already ran runs twice.
- Completed
Approved
The action runs with exactly the details the reviewer saw.
- Failed
Rejected
By default, the run stops with the reviewer's reason.
- Completed
Rejected, and the agent adapts
If you allow it, the agent gets the reason and takes another route, such as a free date change instead of a refund.
- Like a rejection
No decision in time
After the time limit, the request counts as rejected.
The gate lives in the agent file, next to the tools.
List which calls need a person, under which condition, and what the agent may ask for. Tests can approve, reject or time out requests before a deploy.
version: "1.0"
name: travel-desk
description: Handles trip changes for group and business travelers
model: connic/gpt-5.6-luna
system_prompt: |
Handle trip changes within the fare rules.
Explain each change in one sentence for the reviewer.
tools:
- bookings.get_booking
- flights.search
- portals.release_seats
- bookings.rebook_group
approval:
tools:
- bookings.rebook_group: param.change_fee > 500
inputs:
- get_portal_code:
prompt: Ask for the airline portal's one-time code.
label: Airline portal code
sensitive: true
params:
- portal: str
- reason: str
timeout: 1800
message: Check the fare rules and the new times before you approve.
on_rejection: continuebookings.rebook_group: param.change_fee > 500Only costly changes wait
paramreads the tool's arguments andcontextreads values from middleware. Changes with a fee up to €500 go through right away. A condition that can't be evaluated pauses the call.get_portal_codeAsk a person for a code
connic turns
get_portal_codeinto a tool. The reviewer types the code, andsensitive: truemasks it and redacts it from logs and traces.timeout: 1800Half an hour to decide
timeouttakes anything from 30 seconds to 7 days and defaults to one hour.on_rejection: continueRejections the agent can work with
With
continue, the agent gets the reviewer's reason and decides what to do next. The default,fail, ends the run.