Current + 1Stream (BVoip) integration
Your 1Stream calls matched to the right company and person, with who is calling before you answer and the call's note and time ready after.
Current connects to 1Stream by BVoip with a Client API key and reads your calls, the lines they came in on and 1Stream's call analysis, matching each call to the company and person it was with. An optional Control API sign-in adds the health of the customer phone systems you resell.
Status
Current built this connector from 1Stream's published API. Its Client API has been read once, read only, from a live 1Stream account; the rest has not yet been checked against a live account. If a figure looks wrong after you connect, support reads the card's sync record first.
What it does
- An incoming-call card for the person whose extension rings.
- After the call, a wrap-up with a suggested note, next steps and time, once a tenant admin confirms your greeting tells callers that calls may be recorded and transcribed; the person changes anything and presses Save. Without that, Current keeps the call's details only.
- Call history on company and contact pages.
- A callback owed for a missed or abandoned call, which closes itself when someone reaches the number.
What Current never keeps
Recordings and full transcripts are never stored. Current reads a call's transcript once to write the note, next steps and coaching, then lets it go; coaching keeps at most four short redacted excerpts from a call, seen by the engineer and their pod lead. A recording plays from 1Stream for the people allowed to hear it. Screens show only a number's last four digits. Dialling a contact, signing people in and out of call lines and paging the on-call rule are off until a tenant admin turns them on.