CentrusOstara

client portal · read and write

Work orders accepted. ETAs already written.

Centrus integrates with Ostara for UK field service businesses. Agents accept the order inside the SLA window, write the ETA, and send attendance back to the client's portal. Ostara stays the portal your client runs.

Book a demoWhat it covers

start with these

Someone logs in to Ostara all day to accept orders and type in ETAs.

Give Centrus a work order number in Teams or WhatsApp. It reads the order, and accepts it or sets the ETA once you confirm. Agent Builder starts the work order on Ostara when the engineer starts the visit, then stops it and adds the notes when the job is done. The portal stays the client's.

  1. 01

    Accept the work order from Teams

    The desk gives the work order number. Centrus reads it, and accepts it once they say yes.

    Works with Teams, Ostara

  2. 02

    The ETA set from the van

    The engineer sends an ETA. Once they confirm, the client sees it on the work order.

    Works with WhatsApp, Ostara

  3. 03

    Attendance that matches the van

    When the engineer starts the visit in the job system, the work order is started on Ostara too.

    Works with Ostara, BigChange, Joblogic, Simpro

  4. 04

    Notes on the work order when it's done

    When the job is completed, the work order is stopped and the engineer's notes go on it for the client.

    Works with Ostara, BigChange, Joblogic, Simpro
01 / 04

more with Ostara

setup

Three details, then the webhook

Connect Ostara on the agent with the username, the API key, and the client host short name. The webhook is a second step in the Ostara portal.

01

Connect Ostara

Enter the Ostara username, the API key Ostara emailed when they granted API access, and the client host short name. The first connect also creates the webhook username and password you paste into Ostara.

How to connect

02

Build the first agent

Start with a work order number you already have. Describe the run in Agent Builder: open the order, accept it, raise the job. Ostara takes one request at a time per user, so the agent waits its turn.

03

Register the endpoint

In Ostara, add a webhook endpoint, tick Job Started and Job Stopped, and ask Ostara to whitelist the URL. From then on, a start or a stop on the portal starts the agent you built for it.

Start an agent from Ostara

what it covers

The work order, and the actions on it

Ostara is opened by work order number. There is no list of every open order on the public API. Each agent reads the order, then writes to it, and Ostara posts a job start or stop to begin a run.

connects through
An Ostara username, API key, and the client host short name
reads and writes
Work orders, accept, ETA, start and stop, notes, documents and authorisation
starts on
Job started or stopped in Ostara, a BigChange job change, or a schedule
works in
Chat on the web, WhatsApp and Teams, and Agent Builder

  • Work orders

    agents read

    Open one work order by number

    agents write

    Create a work order against a building, with the contact and the task

    starts a run

    Schedule or chat

  • Accept and ETA

    agents read

    Read whether it is accepted and any ETA already on it

    agents write

    Accept the job, write or update the ETA, set the client reference

    starts a run

    Schedule or chat

  • On site

    agents read

    Read start and stop times already written

    agents write

    Start travel, start the job, pause it, or stop it

    starts a run

    Job started and job stopped, posted by Ostara

  • Notes and files

    agents read

    Read notes and documents already on the order

    agents write

    Add notes, attach a document, or add a certificate

    starts a run

    Schedule or chat

  • Authorise or refuse

    agents read

    Read whether it is waiting on authorisation

    agents write

    Authorise, refuse, or cancel the job, with a note

    starts a run

    Schedule or chat

  • Engineers

    agents read

    Read who is logged on

    agents write

    Log an engineer on or off against the contract

    starts a run

    Schedule or chat

Ostara can start the run. A start or a stop is enough.

Register an endpoint in the Ostara portal and tick Job Started and Job Stopped. Each one starts a run with the work order attached, and no credits are used while nothing happens. Ostara stays the portal the order lives in.

See how chat and agents work in Centrus
previous integrationFixfloAsk what is logged on an issue, write your job number back, and update the managing agent on the portal.next integrationCin7Ask what is on the shelf or what a customer last bought, and get the offer sheet built.

questions

Ostara questions

Agents built in Agent Builder open a work order by number, accept it, write an ETA, start or stop the job, add notes or documents, and authorise or refuse further works. A run starts when Ostara posts a job start or stop, when a BigChange job changes, on a schedule, or from chat once the agent is published.

No. Fixflo is a housing repairs portal. BigChange is the job you run. Ostara is the client work-order portal the contract already sits in. Connecting Ostara does not connect Fixflo or BigChange.

No. Ostara stays the portal your client runs, and the contract sits there. Centrus opens one work order by its number and writes the acceptance, the ETA or a note onto it, so the client sees the update in Ostara.

That AI only sees what lives inside Ostara. It does not see your job system, your inbox, your documents or anything else running the business day to day. Centrus sits across everything you use, so it is not limited by what one vendor decided to build.

No. Ostara's public API opens one work order by its number, and there is no list path. Chat and agents start from a number you already have, or from the job start and stop events Ostara posts.

Yes. In chat, someone opens one work order by its number and, after they confirm, Centrus can accept it, set the ETA, add a note or set the client reference. Agent Builder can start a run when Ostara posts a job start or stop. Neither lists every open order.

Username, API key, and the client host short name. The short name is the first part of the Ostara host, the bit before -ostaraapi. Ostara emails the API key when they grant access.

Ostara posts job started and job stopped to your endpoint once it is whitelisted, and each one starts a run. A BigChange job change, a schedule or an email can start an Ostara agent too.

No. Your data is not used to train AI models, and training is switched off on our AI provider account. Data is encrypted in transit and at rest, and access is set per person through tags and roles.

Ostara comes with every plan, from £299.99 a month. Agents use automation credits, and a webhook trigger uses none while nothing happens. Plans run month to month, with no lock-in, and paying annually saves 20%.See full pricing
Centrus AI

in the 30 minutes

  1. 01We start with how your operation actually runs, on the desk and in the field.
  2. 02We show the agent that accepts an Ostara work order, raises the job and writes the ETA back as the engineer sets off.
  3. 03We pick out the admin that should run itself first.

See it working with Ostara.

Found the use case you need, or doing something that isn't on the list? Book 30 minutes. Bring the job you want handed over, and we will show it on a setup like yours. You leave with a plan.

30 minutes / UK team / No lock-inOr see pricing