Introducing KYA (Know Your Agent) on Chatbase Personal agents are here, and communication between consumers and brands will grow by orders of magnitude. These agents check on orders, change bookings and ask about plans, all on their human’s behalf. You need an agent that represents your business and gets... your customers (and their agents) what they came for. That’s what we’re building at Chatbase. We’ve partnered with Persona to develop our KYA solution. Personal agents can authenticate with your business, and you decide exactly what these agents are allowed to do. Your customers can customize the permissions and access they give to their personal agents. If you're interested in this for your business, sign up using the link below!show more

@chatbase agents doing business with other trusted agents - every business should do this!

@chatbase Generational camo 🙈

@chatbase so proud of the team on this one. personal agents are coming either way, now businesses actually have a way to say hi back

@chatbase that's awesome!!

@chatbase always ahead of the race

@chatbase Bullish

@chatbase dooooope

@chatbase insane!!!

@chatbase let's goooooo!

@chatbase Yo this is fire

@chatbase never stop pushing boundaries 🫡

@chatbase 🫡

@chatbase You are executing so well

@chatbase the personal agent era is upon us!

@chatbase This is crazy

@chatbase Congrats team 🔥

@chatbase you're so good at this man

@chatbase Haha thank you!

@chatbase the customer picking what their own agent is allowed to do on the brand side is what support teams will actually care about, what happens when an agent asks for something outside its permissions, hard no or does it hand off to a human

@chatbase we building discovery, onboarding (KYA) and payment for agents. Let's chat!

@chatbase congrats bro 🚀

@chatbase 🙏

@chatbase agent takeover has started

@chatbase Allow or deny per action makes sense. Healthcare needs a third option: "ask my human first". A patient's agent can move an appointment, but test results only go out once the patient taps yes in the moment. Is that on the roadmap?

@chatbase So tuff

@chatbase customers setting the permissions themselves is the part i'm curious about. does the business see what my agent is allowed to do up front, or only find out when it asks for something

@chatbase per-agent permissions are the right model. the next thing both sides will want is a trail per action: when a personal agent changes a booking the human didn't actually want, the brand and the customer both need to see which permission allowed it

@chatbase Damn, Chatbase as an A2A layer is a big brain move

@chatbase this is awesome

@chatbase this is the part nobody’s talking about yet. everyone’s building the agent, not the “is this agent actually allowed to do this” layer. curious how you handle scope when my agent wants to do something i never explicitly approved?

@chatbase the permissions part is where every agent product gets messy

@chatbase super cool!

@chatbase At one end I feel jealous of you, and at another end I feel you deserve all the success. Congrats.

@chatbase who said dots are this small?

@chatbase How does this handle an exception agreed by phone, say, "move the booking, but keep the rate Sarah promised"? Would the personal agent need to supply that context, or could the business agent recover it?