TITVSView Plans

Work through a schedule change with the whole picture.

A changed appointment can affect a customer, a crew and the next job in the day. Dispatcher is an included managed agent for job routing and scheduling workflows. Titus coordinates the context and handoffs around the systems and rules agreed for your deployment.

Discuss this workflowSee an example

01

Capture the constraints before proposing a change

A workable change needs more than a requested time. Decide which details matter for your operation: the job, people affected, location, access window or another dependency. The workflow should identify missing information before treating a suggestion as a decision.

Start with the schedule your team actually uses. Setup establishes which source can be read, which actions are supported and who owns a conflict. Mentioning a calendar or job system does not connect it or grant permission to change it.

02

Separate an option from an approved update

Dispatcher can be scoped to prepare an option for review or to take specific authorized actions under agreed rules. Define which changes need approval, how conflicting requests are handled and when a person must choose between alternatives.

A proposed time should not be described as confirmed until the relevant action succeeds. Discuss how the workflow responds if an update fails or the schedule changes while a decision is pending. A person needs a clear way to resolve that exception.

03

Carry the decision into the handoff

Agree which people need the approved change and through which configured channel. Customer confirmation and crew coordination may involve different agents or systems; the same decision should be carried into each handoff.

Titus orchestrates the connected agents you choose. Receptionist can be part of a confirmation workflow where configured, and is included in both plans, but is not activated merely because Dispatcher is configured. Each role has its own scope and permissions.

04

Test the awkward cases

Use examples from your operation: no suitable slot, an unavailable crew, two requests for the same appointment and a customer who changes their mind. Verify what is recorded, who is asked and what remains pending.

The setup discussion covers connected systems, the allowed actions, human ownership and review. We do not promise support for every dispatch platform, automatic route optimization or unrestricted calendar changes. Confirm the actual workflow and commercial terms before starting.

Illustrative workflow

A customer needs to move tomorrow’s visit

  1. 01

    Titus captures the customer request and identifies the affected job.

  2. 02

    Dispatcher checks the authorized scheduling source and prepares an option.

  3. 03

    The change reaches the required person for approval.

  4. 04

    The configured update and confirmations follow the approved decision.

Explore the interactive Titus examples →

An example to discuss during setup. Available actions depend on the connected systems, selected agents and approval rules configured for your business.

Before you start

Will Dispatcher change my schedule without asking?

Only actions explicitly authorized in the setup may happen automatically. Agree the changes that need a person and how exceptions are handled.

Does this include route optimization?

Do not assume it does. Job routing and scheduling scope depends on the connected systems and agreed workflow; optimization requirements need a separate capability check.

Do crews need to use a new app?

The channel and handoff are discussed around your current operation. Availability must be confirmed for the people and systems involved rather than promised universally.

Bring one task you want help with.

Tell us how it works today, which systems are involved and where a person must make the decision. We will confirm the scope, available actions and commercial terms before you start.

Discuss your setup