What We Publish on LinkedIn cover illustration

## Who this channel is for LinkedIn is the channel aimed at the people who actually make the decision to deploy a voice agent: heads of support and operations, contact centre leads, and the founders and product managers who own the phone experience. That shapes what we post. The bar is whether something would be useful to a person weighing whether voice AI is worth their team's time, rather than whether it performs well as a post. If you are an engineer wanting implementation detail, X is the better follow; if you want to watch the product work, YouTube.

## What we post here Four things, roughly. Product changes, when something ships that changes what you can build rather than every internal increment. Industry analysis — what is actually changing in voice AI, including the parts that are overhyped, which we would rather say plainly than pretend not to notice. Practical breakdowns of problems teams hit in deployment: escalation design, why containment rate misleads, what testing a voice agent really involves. And hiring, when we are hiring. What we try to avoid is the reflex of restating our own homepage, which is the failure mode of most company LinkedIn accounts. ## Where the longer arguments start Several of the pieces on this blog began as LinkedIn posts that got argued with in the comments and turned out to be worth expanding. That is deliberate: it is a cheaper way to find out whether a claim survives contact with people who run phone operations for a living than writing two thousand words first. If you want to influence what we write about at length, disagreeing with us there is the most direct route. ## Frequently asked questions LinkedIn is the channel aimed at the people who actually make the decision to deploy a voice agent: heads of support and operations, contact centre leads, and the founders and product managers who own the phone experience. That shapes what we post. Four things, roughly. Product changes, when something ships that changes what you can build rather than every internal increment. Several of the pieces on this blog began as LinkedIn posts that got argued with in the comments and turned out to be worth expanding. That is deliberate: it is a cheaper way to find out whether a claim survives contact with people who run phone operations for a living than writing two thousand words first. ## Try Persistence Design, test, and deploy production-ready voice agents. ## Continue reading