Welcome back.
Continue with your company?s existing sign-in.
Explore the demoInvocursor operator sign-in
InvocursorInvocursorContinue with your company?s existing sign-in.
Explore the demoInvocursor operator sign-inSee what was prepared, what was verified and what still needs a person.
Sign in to your private operator workspace.
Owner access only. Contact your Invocursor operator if you need access.
See workflow outcomes, a support queue, booked meetings and team availability. No sign-in needed.
Accepted requests over the selected period.
| Date (UTC) | Requests |
|---|
Approved steps were proposed. A saved result is not yet confirmed.
The customer’s authenticated system confirmed the saved result.
A user or support team explicitly confirmed resolution.
Manage access for the selected integration.
Pausing or rotating revokes existing customer sessions. Keys stay in the customer’s backend; customers do not need an OpenAI key.
Confirm the permitted pages, roles, controls and customer storage endpoint before enabling the integration.
Transfer this through your approved secrets channel to the customer’s backend. Never put it in browser code.
Fixed outcome counts, not conversations. No transcripts, email addresses, page URLs, form values or support-ticket text are available here. Operational events are retained for 30 UTC date buckets; integration configuration has a separate lifecycle.
Requests are processed transiently through Invocursor and OpenAI. Provider retention is separate; approved Zero Data Retention is not asserted. Request counts are not billable conversation totals.