Skip to content
Current

1Stream: calls, queues and coaching from your phone system

Connect 1Stream by BVoip with a Client API key and every call reaches the right person, ticket and company: who is calling before you answer, the note, time and next steps ready after the call, live queues, callbacks that close themselves, and private coaching. An optional Control API sign-in watches the 1Stream phone systems you resell.

Updated 12 min read
On this page · 12 sections

What it does for you

Where in CurrentWhat you get
When the phone ringsThe person whose phone rings sees who is calling, their company, anything urgent going on for them (an outage, a callback you owe them, an unhappy last call) and their open tickets, before saying hello. Nothing opens by itself and nothing plays a sound.
After the callThe call becomes a record with a short note, next steps and the time already filled in, on the ticket you had open when you answered. One press saves it all. Call time goes to your PSA only from the side you choose, so it is never billed twice.
Dispatch and Up nextYour queues live: who is waiting and for how long, who on each pod is on a call, wrapping up or logged out, and the callbacks owed. A pod week shows each pod's service level.
CoachingEach answered support call is scored on six habits with the evidence beside each score. The engineer and their pod lead see it, nobody else.
Company and contact pagesEvery call with that company or person for 90 days, with its summary. An unhappy call reaches the account manager the same day.
Their phone systems (optional)With the Control API sign-in, the 1Stream phone systems you resell show their health on the partner's page, like backups, and raise an alert when one goes offline or loses a trunk.

1Stream by BVoip runs your business phones. Current reads your calls, your queues and 1Stream's call analysis, matches each call to the company and person it was with, and puts what matters on the records your team already works. Current only reads 1Stream, apart from three things a person presses and a tenant admin turns on: ring your own phone to dial a contact, log people in and out of queues, and page your on-call rule.

Two parts, one connection

PartNeeded?What it reads
Your 1Stream key (Client API key)RequiredYour own help desk: call logs, live queue and extension status, recordings on demand, and 1Stream's call analysis. It also lets a person ring their own phone to dial, and log in and out of queues.
Control API sign-in (1Stream calls it the Partner API)OptionalOnly the health of the 1Stream phone systems you resell: extensions online, trunks, high availability and calls in use.
Note
What Current keeps, and what it never keeps
For each call Current keeps the time, the direction, the queue, who answered, how long the caller waited and talked, the number's last four digits on screen, the company and contact it matched, and a short summary with next steps. Call transcripts and recordings are never stored: Read transcript and Listen fetch them from 1Stream each time, for the people allowed to see them, and keep nothing. Your 1Stream key is stored sealed and is never shown again, only a short fingerprint so you can tell which key is saved. Calls older than 90 days are deleted. Partner viewers never see any of it; that is enforced in the database.

Connect 1Stream

  1. 1
    Create a Client API key
    A 1Stream admin opens the 1Stream Admin Portal, goes to Administration > Manage Organization > Client API Keys and creates a key named Current. 1Stream shows the key once, so copy it now. Your account needs 1Stream Core or higher.
  2. 2
    Paste it into Current
    In Settings > Integrations, open 1Stream by BVoip in the Phones group and press Set up 1Stream. Pick your region (North America if you sign in at portal.1stream.com, Europe or Asia Pacific if you sign in at portal-eu.1stream.com), paste the key and press Connect. Current checks it with one read of today's calls.
  3. 3
    Send calls as they happen
    Press Make the address and copy it. In 1Stream open Administration > Manage Organization > WebHook Registrations and add one registration for each event: CallRinging, CallConnected, CallEnd and TranscriptionReady. Call your main number from a mobile and the setup shows it arrive. You can skip this; calls then arrive every 5 minutes and nobody sees an incoming call card.
  4. 4
    Match your team and your queues
    Check that each 1Stream extension belongs to the right person. Put each queue in a pod, set its answer target, and tick any after hours or on-call queue and any test queue. A queue in no pod is called out until you pick one.
  5. 5
    Make your choices
    Choose who writes call time to your PSA, set the callback target and the unhappy call alerts, and confirm that your greeting tells callers calls are recorded. Then press Turn on.
  6. 6
    Watch your partners' phone systems (optional)
    Later, open the setup's last chapter, sign in to 1Stream's Control API (which 1Stream calls the Partner API, at controlapi.bvoip.net) on 1Stream's own page with read access, and match each phone system you resell to its partner.

Answered or connected

1Stream marks a call answered when a queue picked it up, which includes calls that went to voicemail. Current counts a call as connected only when a named person on your team spoke with the caller: an extension that belongs to a person, and talk time above zero. A call that reached a voicemail box is voicemail, and everything else is abandoned. Only connected calls credit an engineer, get coaching, or count as answered on any board or report. A caller who hangs up within the missed-call threshold (10 seconds by default, counting the greeting) is treated as a wrong number: it is shown, never hidden, and it costs no queue and owes nobody a callback.

Who logs call time

If 1Stream already writes call time into your PSA, choose 1Stream logs call time and Current makes no time entry for calls. If you choose Current logs call time while 1Stream is still linking calls to your PSA, setup asks you to turn off 1Stream's time entries there first, because otherwise the same call is billed twice. Time already in your PSA is never changed.

Callbacks

A missed, abandoned or voicemail call from a number that is not one of your own owes a callback, one per number at a time; a second miss adds to the first. It belongs to the pod that serves the company and is due within your callback target (60 minutes by default). It closes itself when someone reaches that number for 20 seconds or more, or when the caller calls back and is answered. Anyone can also mark it Reached another way, or Not needed.

After the call: wrap up

When the call ends, the call card says Wrap up your call. Press it and Current shows the ticket it thinks the call belongs to (the one you had open when you answered comes first, and each choice says why it is there), the note it wrote from the call, the next steps and the time. Change anything, then press Save. The note goes on the ticket as an internal note, the time is logged through the desk's own time entry, and each next step becomes what you picked: part of the note, a to-do for you, or a callback with a due time. Undo works for 10 seconds.

Tick Also send a summary and, after Save, the ticket opens with its Reply box holding a short summary of the call and the next steps, written for the caller. Nothing is sent until you read it and press Send. If the Reply box already has your words in it, Current leaves them alone and adds nothing.

Unhappy call alerts

1Stream scores each analysed call's mood from 1 to 10. A call at or below the low threshold (6 by default), or one Current reads as frustrated or angry, tells the company's account manager through Hot tickets, and a call at or below the severe threshold (3) does too, at once. Changing a threshold applies to new calls only.

SettingWhat happens
OffNo unhappy call alerts. Calls still show their mood on the call record.
Dry runFor a week Current lists the calls it would have flagged and tells nobody, so you can check the thresholds first. This is where setup starts.
OnEach low or severe call alerts the company's account manager. Three low calls from one company in 7 days say so in one line, and a transferred call waits up to 3 hours for its other legs before it counts.

Calls on the service desk

Where the service desk is on, the desk's row gains a Calls tab once 1Stream is connected and coaching is on. Mine lists your own calls of the last 30 days with your coaching. Pod is for the lead of a pod: the pod week, coaching moments, call of the day and call of the week, the long-wait review and each person's figures, sorted by name. All calls is for service managers and tenant admins: team averages only. Without a 1Stream connection the tab is not there at all.

On My Day

  • Callbacks owed to you, and the unassigned ones of your pods, sit in Your work beside your tasks and tickets, in the same order of what is most urgent, with their due time as the deadline: Call back Maria Lopez, Harbor Dental, missed 9:12 AM, due 10:12 AM. A Call button rings your phone first, then dials them. A callback past its time moves up as overdue.
  • Calls to wrap up shows the calls you answered that are not on a ticket yet, each opening its wrap-up. It is not there when there are none.
  • One quiet line gives your coaching for the last 7 days, for example Coaching for 6 calls in the last 7 days, average 4.3 of 5, with a link to Calls. It shows only to you.

Reports, dashboards and scorecards

The Service report gains a Phones section for the dates you pick, compared with the period before: calls in and out, answer rate (calls a person answered, out of the incoming ones), service level, average wait with the time 9 in 10 calls were answered within, abandoned calls (voicemail and wrong numbers shown apart), callbacks on time, incoming calls by hour, and how many calls were put on a ticket. Scheduled PDFs read it as the person who receives them. Coaching is never in a report.

Dashboard metricWhat it counts
Callers waitingCallers in a 1Stream queue right now, across every queue.
Longest waitThe longest current wait in a queue, in minutes.
Calls answered todayIncoming calls a person answered today.
Calls abandoned todayCallers who hung up before anyone answered today.
Callbacks past dueCallbacks owed past their target time.
Available to take callsPeople logged in to a queue and free right now.
Phone service levelCalls a person answered within the queue's answer target, out of the calls offered, over the dashboard's dates.

Every Phones metric is a count with no caller named, so all seven show on a TV dashboard too; on a TV, Phone service level shows today only. Four scorecard numbers can be given to a person or a team: Phone answer rate, Callbacks on time, Average phone wait and Team call coaching average. A person's own coaching average is never a scorecard number.

Who sees what

WhoWhat they see
The person rungThe incoming call card for their own calls, and the call record afterwards.
Service desk staff and dispatchersThe live queues and callbacks on Dispatch, and calls on the tickets they can open.
Account managersCalls on the companies and contacts they can see, and unhappy call alerts for their book. Never coaching.
FinanceCall counts in reports only. No transcripts, no coaching.
Partner viewersNothing from 1Stream, anywhere.
Heads up
1Stream has not sent a call event lately
When live events are set up and nothing has arrived for 30 minutes during business hours, the 1Stream card says when the last event came. Check the WebHook Registrations in 1Stream, or make a new address and paste it there.
Heads up
If the address may have leaked
Treat the webhook address like a password: anyone who has it can send pretend call events into your workspace. Current only reads a call's words when the call is one 1Stream itself recorded for your workspace, on the extension the event names, so a pretend event cannot start a call summary on its own. If the address may have been seen by someone it should not have, a tenant admin opens 1Stream by BVoip in Settings > Integrations, goes to the live events step and presses Make a new address. The old address stops working at once. Paste the new one into each of the four WebHook Registrations in 1Stream straight away, or no live events arrive until you do.
Was this helpful?