Features
Know how many people you need, hour by hour
From your last twelve weeks, Hivenza forecasts the contacts per channel, weekday and hour, works out the people needed, suggests shifts from your own templates, and shows whether people kept to the rota.
Get startedOn Enterprise.
From history to a rota
- 1
Read the history
The last twelve weeks, recent weeks counting more.
- 2
Forecast
Contacts per channel, weekday and hour.
- 3
Work out the people
People needed each hour for the reply time you set.
- 4
Suggest shifts
Chosen from your own shift templates.
What it does
It says plainly when it doesn’t know enough.
- Holidays
- Days the brand marks are left out of the history and forecast as a share of a normal day.
- Handle time
- Set by you, or measured from logged ticket time, or assumed at 6 minutes and said so.
- Shifts
- Chosen from the brand’s templates, including overnight shifts.
- Rota
- Giving a person a shift writes their rota, and the change is audited.
- Adherence
- Scheduled against actual, by person, day and hour.
- Not enough history
- Under three weeks or fifty contacts, it forecasts nothing and says so.
EnterpriseSee plans and prices
On Enterprise
Staffing forecasts are part of Enterprise, with their own permissions to view and manage.
Questions
How good is the forecast?
It is tested against known history; with too little history it declines to forecast.
Does it schedule people automatically?
No. It suggests shifts and a person gives them.
Which plan includes it?
Enterprise.
Goes well with
- Workflows
- Campaigns
- AI knowledge
- AI procedures
- AI quality
- Routing and supervision
- WhatsApp calls
- CRM sync
- Known issues and case status
- Reporting and API
- Content library
- Website analytics
- Reviews
- Employee advocacy
- Paid ads
- Listening
- Analytics and reports
- Plan and publish
- Links and link in bio
- Ticket processes
- Customer portal
- Ticket apps
- AI memory
- Configuration sandbox
- The shared inbox
- Webhooks: Zapier, Make, n8n
Staff for the hours that are busy
