Changelog

Follow up on the latest improvements and updates.

RSS

new

improved

Calendars

Quick View Appointment Details

When you open up an existing appointment you will first see a new quick view in the Appointment Details tab. This allows you to see quickly see key points about an appointment. It also includes key details from the contact that the appointment is with like name, phone, email, and address.
You'll be able to click on the contact's name to go the contact's detail page.
Phone appointment? Just tap on the contact's phone number right there to call them.
In-person at their address? Just tap on their address to open it in Google Maps!
Additionally, the contact section will display any contact fields that you have selected for the Internal Summary for the calendar where the appointment is booked.
To reschedule, or otherwise edit the appointment, just tap on the Edit tab and you will see the traditional view that allows changing the time, assigned team member, status etc.
Screenshot 2026-09-17 at 5
Conditional disqualification in calendar widgets
You can now set rules in widget settings for a specific calendar to disallow booking. based on any contact field you are gathering in the widget.
For example:
If you only want to book with people in New York or New Jersey you could set a rule like this:
Screenshot 2026-09-17 at 1
You get to choose the disqualification message people see when their booking is refused.
Screenshot 2026-09-17 at 2
To add a conditional booking rule for a widget, go to
Appointments & Calendars
>
Calendar Settings
> click on a calendar > go to the
Widget
tab >
Conditional Booking Rules
Note:
calendar widget conditional booking rules only apply to bookings through a public calendar widget. They do not apply to appointments created from inside your account in
brayv.ai
or to bookings made by
AI Agents
.
AI Agents already had the ability to disqualify a lead using a conditional tool.
Embeddable public widgets for calendars are now more dynamic.
In larger containers on web pages they are embedded in they will expand more: logo, widget title, and description to the left; calendar to the right, while still being optimized for smaller spaces / views on mobile. This allows you to take up more visual real estate on a web page when you want to.
Screenshot 2026-09-17 at 1
This is dynamic so no changes are required from you for this to take effect.
Two new options give you finer control over how AI booking rules balance appointments across your team.
Exclude a calendar from load balancing
Not every calendar should influence who gets the next lead. Service calls, internal meetings, and follow-up visits can now be left out of the appointment counts your routing rules use.
Open any calendar's settings and check
Exclude from load balancing
(just below User Selection Strategy). That calendar's appointments immediately stop counting toward team members' rolling 30-day totals
for every set of booking routing rules in your account,
with no changes to your existing rules. The calendar stays fully bookable and selectable; only the load-balancing math changes.
Screenshot 2026-09-04 at 3
Per-calendar appointment counts in routing rules
Rules can now look at appointment counts for specific calendars instead of just the whole account. This unlocks calendar-scoped balancing and percentage splits, for example:
  • "80% of the appointments in the the North Calendar should go to John; the rest can go to any other available user."
  • "70% of the appointments in Calendars A and B go to Jake, Sally, or Tom."
Screenshot 2026-09-04 at 12
Just describe the rule in plain language when setting up AI Calendar Selection and the new
User Appointment Counts by Calendar
variable is used automatically. It's also available in the variable picker, the Distribution Quick Guide, and the saved-script tester, where you can generate sample per-calendar counts to see which branch a rule takes.
Good to know
  • Percentage rules are measured over the rolling 30-day window of appointments in the named calendar(s).
  • Excluding a calendar removes it from the global and by-ZIP counts, but per-calendar counts still include it, so a rule that explicitly references that calendar keeps working.
  • In Atlas, you can ask to "stop counting the Service calendar toward rep load" and it will update the calendar setting for you. Ava Code Mode understands the request too but will point you to the checkbox rather than writing a rule around it, since excluding a calendar is a calendar setting, not a routing rule. Ava can still build the percentage-split and calendar-scoped rules directly.

new

AI Text Agents

AI Voice Agents

New Variables (Dynamic Fields) Available

You can now reference
{contact.owner_first_name}
and
{contact.owner_last_name}
in multiple contexts to dynamically fill in the assigned team member's (the contact owner) name.
This can be accessed in
message templates for conditional tool actions
like notifications to your team (eg internal email and SMS), and SMS sent to the contact via conditional tools
or agent follow ups.
Screenshot 2026-08-31 at 2
This can also be used in agent
instructions
if you want the agent to be aware of who the assigned team member is.
Screenshot 2026-08-31 at 2
Not recommended in agents handling new leads where the assigned team member isn't chosen till after an appointment is set in case your assignment switches at booking, but can be useful if you assign early/at lead submission and you always book with the assigned team member.
Agents are always only aware of the information you specifically choose to reveal to them.
To access variables in most editor interfaces (instructions, message templates, etc.) simply type the
{
key on your keyboard and the dropdown selector appears.
Appointment Variables
: for appointment confirmation and reminder notification messages, these variables do not appear. Instead, use the pre-existing appointment owner name variables.
(once an appointment is set for a specific team member, that team member also is the contact owner).

improved

AI Text Agents

AI Voice Agents

End Journey actions now require a defined outcome

Agent actions can no longer mark an opportunity as the ambiguous status “ended.”
Going forward, an
End Journey
action must
Mark as Lost
and include a reason (pick a preset, or add your own). If the AI is done on a positive side path that didn’t reach the main goal, use
Complete Journey
instead.
Why this change: ended is now reserved for cases where there really was no defined outcome — for example, follow-ups ran out, or an appointment was canceled after the goal was already reached. That keeps reporting cleaner because you can actually see what happened with your opportunities:
completed
(positive outcome, AI's job is complete),
lost
(with a reason - which can be filtered for), or truly
ended
(system level closure, not a direct action by human or ai), and of course
won
(which can only be set manually by a human click).
What you’ll see:
New
End Journey
actions only offer
Mark as Lost
plus a required
reason
.
Voice agents now have the same Lost / Completed choice, including
Complete Journey
.
If an existing agent still has a “Mark as Ended” action, you’ll get a red indicator on the Actions tab and on the tool itself. You won’t be able to save other changes until you either switch it to Mark as Lost with a reason, or replace it with Complete Journey.
Existing agents keep working as they are until you edit and save them.
There was a login issue affecting ~10% of users on our latest version of the Android app. This has now been resolved.
If you are experiencing this issue, please open the Google Play Store, search for
brayv.ai
and install the latest update (Dated Aug 28, 2026)
After installing the latest update login should resume working.
If you still hit issues after installing the latest update please let us know at support@brayv.ai
latest google update
Inbound calls on your primary number can now ring the right person automatically. When your call routing is set to
Transfer directly
, you'll see a new option:
Ring the assigned team member when available
.
With it turned on, when a customer calls in, we look up their contact record — if they have an assigned owner and that team member has a phone number on their profile, the call transfers straight to them instead of ringing to your general direct transfer phone number.
If the caller is new, unassigned, or their owner doesn't have a phone number configured, the call falls back to your regular transfer number, so nothing slips through.
To enable it:
Go to
Settings
→
Phone
and open the routing settings on your primary number
Select
Transfer directly
and check
Ring the assigned team member when available
Make sure your team members have their phone numbers set under Settings → Team (or Myself)
Perfect for sales teams and service businesses where customers should reach the rep who owns their relationship — not whoever happens to pick up.
Screenshot 2026-08-26 at 5
Not applicable when you are ringing in app
- that already rings the assigned team member + anyone who has a role that gives them access to all contacts (as long as they are logged in).
This can be used in combination with the Voice AI: If your primary number transfers directly to a Voice AI agent already, you can add the setting for
Ring the assigned team member when available
which would skip over the Voice AI and ring straight to your team member's phone if they are the contact owner (and their phone number is set in brayv).
If you always want Voice AI in line first, don't select this setting, and simply have calls on the primary number route directly to a Voice AI number that has an
inbound default
agent. That agent can then be instructed on when it's appropriate to transfer to particular team members.

new

Mobile App

Phone System

Direct In-App Calling on Mobile App

Update
Now available on Android as well.
You can now place calls directly from your mobile app
if you are on iOS. Simply tap on a contact's number from the
AI + More Options
view in a conversation, or tap on the
call
button from a contact page.
This allows you to call from your
brayv.ai
Primary Number
(the same one you text from and call from in the desktop application). Previously on the mobile app, tapping to call would place a call from your phone's dialer, meaning your mobile phone's number would show up as the caller to your contact. Now you can call without worrying about customers having your personal number.
Note, since this is now using the brayv phone system (which runs on Twilio), you need to have a stable data connection (wifi or mobile data are both fine) to have good call quality.
To use the new feature, be sure to update the
brayv.ai lightning
app from the App Store or Google Play Store
IMG_2019
Screenshot_20260826-165936~2
The first time you place a call, the app will request microphone permissions. This must be accepted for your calls to work.
IMG_2020
You will know you are calling within brayv when you see a screen like this instead of your phone's native calling interface:
IMG_2021 copy

improved

AI Voice Agents

Voice AI Agent Improvements

Voice AI Agents now have improved adherence to instructions, and are more concise in their speech.
They are better at sticking to one question at a time in a structured conversation, and overall more concise in responses which leads to more fluid and natural conversations with your customers.
This latest update is showing lower latency, lower speech understanding error rates overall, and significantly lower speech understanding error rates in noisy environments.
We recommend running a web test call or two with your Voice Agents to get a feel for how the latest upgrade of brayv.ai voice agents handles your current agent configurations.
Previously, appointment reminders for your team were sent to the appointment owner and everyone in the calendar's "Additional Team Members to Notify" list. For many teams that meant extra people getting reminder texts and emails for appointments they weren't running.
What's changed:
  • Team reminders now go only to the appointment owner by default
  • A new option in
    Calendar Settings
    >
    Notifications
    >
    Team Reminders
    — "Also send team reminders to the additional team members listed above" — lets you opt back in to reminding the full list
  • Booking confirmations and cancellation notices are unaffected: additional team members still always receive those
How this applies to existing appointments:
reminders are scheduled at booking time, so appointments booked before this release keep their already-scheduled reminders — additional team members will still get those.
The new owner-only default
applies to appointments booked (or rescheduled) going forward.
To keep the old behavior for future bookings, just enable the new checkbox on that calendar.
Screenshot 2026-08-17 at 1
Load More
→