Solutions and roadmap

The week, published and accounted for.

Elaris is being built around the job a planner does every week: build the schedule, publish it, see each interval against what the work requires, and let every person read their own day.

IN DEVELOPMENT

Elaris is in active development and is not generally available.

Solutions

Three jobs. One schedule.

Each job is written twice: once for a contact center, once for any other team that works to a schedule. The schedule is the same. Only the words for the work change.

01 — Publish the week

Build it, publish it, keep the record.

A planner builds a week, copies a day, and publishes it. After that, a change is an amendment: it records who approved it and why, and sits beside the published day instead of overwriting it. A recalculation does not erase that edit.

Contact centers
Publish the week your queues need covered, and keep every later change on the record.
Any scheduled team
Publish the week your team works, and keep every later change on the record.

02 — See the interval

Where is the schedule short, and by how much?

Coverage shows each interval’s requirement, what is scheduled, and the gap between them. A requirement nobody supplied reads Not provided. A zero is a zero. A Break is time on shift but away from the work, so it lowers what is scheduled for its span instead of being treated as if it never happened.

Coverage for one team, four half-hour intervals
IntervalRequirementScheduledGap
09:0066Met
09:3075.5Under by 1.5 one person on a 15-minute Break
10:00Not provided6Not available there is no requirement to compare with
10:3001Over by 1
Illustrative · synthetic figures
Contact centers
See each interval against the agents your queues require.
Any scheduled team
See each interval against the people the work requires.

03 — Read it on a phone

What am I working today?

Each person sees their own published day, laid out for a phone. Times are shown in their own time zone when one is set, and the page says which zone it is using.

Contact centers
Each agent reads their own published day.
Any scheduled team
Each person on the team reads their own published day.

Roadmap

What exists, what is next, and what comes later.

There are no dates. The order is the plan, and nothing here is a commitment to a particular capability or timeline.

Now

IN DEVELOPMENT

The Scheduler path above, working end to end on a synthetic tenant: a test organization with made-up people, not a customer.

  • Manual publish
  • History
  • Coverage

Next

NOT BUILT

A customer can load their own people, including a routing profile, and sign in as themselves. That is the first thing a buyer would need. It is not built.

Later

NOT BUILT
  • Forecasting
  • Break and lunch placement that moves only unlocked breaks
  • A schedule generated from a Work Plan

Shape it against your own operation.

Early access is opening to a small number of workforce teams willing to shape the product against real operational problems.