πŸ€– AI Support Desk

Support team sign-in

NΓ³vare admins: sign in from the main PBX admin instead β€” this box is for support-team accounts.

πŸ€– AI Support Desk

AI-first client support: tickets answered by the AI assistant (or drafted for your approval), change-request approvals, knowledge base, SLAs and reports.
–open tickets
–pending requests
–KB articles live
…
Clients only see tickets/KB/requests while this is ON. Admin preview (impersonation) works regardless.
Per-client support consumption β€” the "are we making money on this account" view. Internal only; clients never see it. Human replies are your time; AI replies cost pennies; πŸ’² = services on the unbilled ledger.

Client support records

ClientAccount agentPlanPhonesTickets (30d / all)OpenHuman repliesAI replies⏱ Time (30d / all)RequestsπŸ’² unbilled / billedCSATLast ticket

☎️ BYO phone lines β€” client-owned trunks

TrunkProvider / serverAuthStateOwned byIf their line dies
Assigning a trunk to a client makes it THEIR line: their outbound calls prefer it, and if their provider drops it (suspended account, unpaid balance, credential change) the sentinel opens a proactive ticket on their account and alerts you. "Fail over" keeps them calling on NΓ³vare's lines while it's down β€” watch those minutes; "block" refuses outbound until their line is back. Create/edit the trunk itself in the main admin β†’ Trunks.

General

Unassigned-ticket, escalation, and SLA-breach emails go to this address. The phone shows under the client's numbers and on the Help tab.

Support team

NameEmailOpen ticketsActiveDesk login
Applies to portal tickets, voicemail tickets, and outage tickets. Assigned agents get the emails for their tickets (assignment, client replies). Unassigned tickets go to the support email above. Add yourself too if you want per-ticket routing.

Response-time targets (SLA)

A ticket waiting on NovΓ‘re longer than its target shows OVERDUE in the queue and emails you hourly until answered.
With business hours on, a ticket opened Friday 4pm with a 4-hour target is due Monday morning β€” not Friday night. Critical severity stays on the 24/7 clock unless you change it.

πŸŽ™ Voicemail-to-ticket

A voicemail on the support line (423-591-5000 β†’ NT Operator β†’ box 504) is transcribed and opened as a ticket on the caller's account β€” matched by their caller ID against client numbers. Unrecognized callers get an escalated ticket for a callback. Blank/no-speech clips are skipped.

πŸ“‘ Proactive outage tickets

A client phone that we've seen online and that stays offline past the threshold gets a proactive ticket with self-help steps (one ticket per client β€” an office-wide outage doesn't flood the queue). NΓ³vare Phone softphones with fresh push tokens are excluded (they sleep on purpose), as are extensions never seen online.
When ON the sentinel pings dark phones at their last-known address (re-opens NAT paths, prompts re-registration), push-wakes silent softphones (and flags ones that ignore 3 wakes), writes a cause diagnosis into each outage ticket (carrier-side vs whole-site internet/power vs one unplugged device), and watches our carrier trunks β€” one automatic re-register, then an ops alert if a trunk stays down.

πŸ“§ Email-in (reply-to-ticket threading)

When ON (and the mail server routing is in place β€” sysadmin task), ticket emails carry a per-ticket signed Reply-To like ticket+42-ab12cd34ef@…; a client's emailed reply lands in the thread, reopens resolved tickets, and wakes the AI front line. Only mail from the account's contact address with a valid signature is accepted β€” everything else is parked and flagged to you.

πŸ“’ Maintenance banners

MessageLevelLiveAuto-hide
Shows at the top of every client's portal the moment it's live; turn it off (or let it auto-hide) when the window is over.

Stale-ticket automation

Applies to tickets waiting on the customer. A client reply always reopens a closed ticket.
AI settings (on/off, draft vs auto, brain, API key) live in the πŸ€– AI Assistant tab.

πŸ“ Location Log

Device GPS locations β€” NΓ³vare-admin only. Download the history, or open the full day-by-day log.
⬇ All history (CSV) ⬇ CSV ⬇ Excel ⬇ PDF Open full log (by day) β†’

Support performance

πŸ“„ Report builder β€” export by client

Each export contains four sections: per-client Summary (tickets, human vs AI replies, requests, πŸ’² billables, CSAT), Tickets, Change Requests, and Billables β€” filtered by the client / dates / search above.

πŸ’² Unbilled services ledger

NOS accounting covers NΓ³vare Digital only today. Every approved billable request (new line, etc.) is recorded here so nothing is given away β€” when NΓ³vare Telecom accounting lands in NOS, this ledger is what gets imported onto client bills. Mark items billed once they're invoiced (manually for now).
#ClientServiceDate

Canned replies (insert into any ticket with one click)

TitleBody
The AI reads each new client ticket message (with their live phone status + the knowledge base) and either answers or escalates to you. Draft mode: it only writes drafts you approve. Auto mode: confident answers go straight to the client, labelled "NovΓ‘re AI Assistant". It can NEVER change PBX config, never touches the approval queue, always escalates critical tickets, and hands off after 3 replies.

Settings

Pasting a key is your go-ahead for the paid Claude API. The key is stored write-only (SIP-credential pattern) β€” it can be replaced or cleared, never viewed. Get one at console.anthropic.com; also store a copy in Vaultwarden.

Activity

Escalated/failed tickets are in the Tickets tab waiting for you β€” the AI never leaves a client unanswered silently. Use "Run AI now" inside any ticket to test (works even while OFF).
Approving a request with a ⚑ kind applies it immediately (rename, VM PIN, VM email, forwarding, DND) β€” a pre-change snapshot is taken first. Everything else is "approved β€” you do it manually" via the normal admin pages.
#ClientRequestDetailsRequestedStatus
#ClientSubjectSeverityStatusSLAAssignedMsgsLast activity

πŸ€– AI draft
⏱ Time on this ticket: 0m

Articles

TitleCategoryLiveViewsπŸ‘πŸ‘Ž

Edit article