Requests, people and connected platforms, in one workspace.
Handle requests from the platforms your business operates. Core ticketing and team tools are included across plans. Capacity varies by plan, and the optional Developer Review Bridge is included only where shown in pricing.
Support
The work your agents do all day, in one console instead of four.
In every plan, including the trial.
- Ticket forms for your business
- Owners and administrators can start with a ticket form template, edit its questions and publish a version for a connected platform. Existing tickets keep their original questions and answers. Your platform needs the form-definition integration once.
- Ticket queues, one per client
- Client sites send their tickets straight into ControlHub over a server-to-server connection. Each lands in its own client queue, unclaimed, until an agent with access to that client claims it. Every change is recorded with who made it and when.
- Chat and voice in the same place
- Chat and voice tools share the ticket context. Available channels depend on your connected platform and the integration setup.
- User vault
- The end-user records behind the tickets, scoped by permission. An agent sees the people belonging to the clients they work on, and nobody else.
Guest on vorld.ioMy card keeps getting declined at checkout.
Amit SharmaI can see two failed attempts. Please try once more now.
Guest on vorld.ioThat worked, thank you.
The team
Keep staffing, coverage and payroll records alongside support when your business needs those tools.
Core team tools are included in every plan.
- Shifts and coverage
- Employees, roles, shifts, time logs and coverage teams. Rosters live beside the queues they staff, so the hours you plan are the hours the work is measured against.
- Payroll in the same workspace
- Pay periods, gross pay, deductions and adjustments for each person, approved and locked record by record. Payout batches are built from locked records and approved before they are marked paid.
- Your bank still sends the money
- ControlHub prepares and tracks payroll. The transfer itself runs through your bank, and its reference is recorded against the batch.
Shifts filled 21 of 21
Clients and access
What your own clients ask about when they run their security review.
Structural, not a setting. It cannot be switched off.
- Connecting a client site
- Each client site connects once over its backend. Heartbeats, success rate and the last event are tracked on every connection, so a silent failure surfaces before the client reports it.
- Company and platform access
- Workspace permissions and database policies separate company records. Platform grants restrict the requests each staff member can access.
- Two checks for every agent
- Inside your workspace, an agent needs the permission and access to that specific client. The application checks both, and a database policy checks the client again. Owners and admins see every client.
| Agent | vorld.io | northwind | halden | kestrel | Visible |
|---|---|---|---|---|---|
| Amit Sharma | ✓ | – | ✓ | – | 9 |
| Rahul Verma | – | ✓ | ✓ | – | 7 |
| Neha Gupta | ✓ | – | – | ✓ | 8 |
| Aisha Khan | – | – | ✓ | – | 3 |
Owner granted Rahul Verma halden.app. Its 3 open tickets are now in his queue.
Oversight
What managers need to answer a question without asking four people.
In every plan, for every client you connect.
- Queue and coverage at a glance
- Open work, unclaimed tickets, tickets inside their SLA window, and how many people are on shift and clocked in right now.
- Health monitoring
- Website checks and heartbeats for every connected client site, with success rate and reliability over 24 hours and 7 days.
- Audit and reporting
- Every action is recorded with its actor and timestamp. Reports draw on the same records the console shows, so what you report is what happened.
- Support B open Thursday shift filled by Rahul Verma
- Amit Sharma escalated TK-2041 to review
- kestrel.shop heartbeat received
- Aisha Khan answered guest chat on halden.app
- Payroll record approved for Neha Gupta, 1 to 15 Oct
How a ticket moves through it.
Intake, ownership and resolution keep the thread intact across agents and shifts. Add developer review when your plan and workflow include it.
Intake
A ticket arrives from a client site and lands in that client’s queue.
Ownership
An agent who holds access to that client claims it and owns it.
Resolution
The agent works it with the customer’s history and context in view.
Optional review
With the optional Developer Review Bridge, a review engineer reproduces a bug and hands the outcome back to support.
See it against your own operation.
Compare included team members, connected platforms and storage on the pricing page. The Developer Review Bridge is an optional capability available on the plans shown there.