Say who’s calling.
The delegate should say it is AI, who it represents and why it’s calling. It must never pretend to be you or borrow your voice to pass a check.
WHY WE’RE BUILDING PROXLING
Getting a repair booked shouldn’t take three calls and your lunch break.
We’re building a little proxy for the things that keep pulling you back in. Someone to make the call, follow up and bring you a clear next step.
It starts with the everyday
01 / SOUND FAMILIAR?
Then came the hold music. The missed callback. The third time explaining what happened.
The repair itself might take half an hour. Getting it arranged can follow you around for days. You become the person who remembers, checks and chases.
That’s the work we want to take off your hands. Proxling starts with a phone number and email of your own, an assistant to follow through, and one place to keep the whole story.
See what handing it over could look likeJust following up on my last email…
Find the reference.
Explain it all. Again.


Whoever answers, it still works for you.
02 / YOUR SIDE OF THE CONVERSATION
A company’s assistant has a job to do for the company. We think you should have someone working for you.
Someone who knows what you asked for, remembers what was promised and checks with you before agreeing to something new.
Longer term, we want your line, permissions and history to stay yours when you change assistants. You shouldn’t have to start from scratch each time.
Less chasing is the first step.
Being properly represented is the bigger idea.
03 / YOUR PERMISSION, MADE CLEAR
The person taking the call deserves a clear answer. We’re exploring a simple way to give them one.
Say you want a repair chased, but you want to choose the date yourself. That should be clear to your delegate and the repair team.
Chase this repair. Discuss dates. Ask before booking or accepting a fee.
A short-lived code opens the permission for that matter, with its limits and expiry.
Withdraw permission and the check should show that it has ended.
This is the flow we’re working towards. A code alone does not prove someone’s identity or replace a company’s own checks.
Try the example. Then withdraw the permission
and check the same code again.

“I’m Proxling, Alex’s AI delegate. My permission code is DEMO-1042.”
Check the code to see the task,
the limits and when to ask Alex.
Now change the permission.
An interactive concept. Nothing is sent and no real identity is checked.
A clearer starting point for a service team.
A route back to the person when they need one.
04 / WHAT WE WON’T LOSE SIGHT OF
Taking work off your plate should make the conversation better for the person on the other end, too.
The delegate should say it is AI, who it represents and why it’s calling. It must never pretend to be you or borrow your voice to pass a check.
Permission is for a specific task. A new charge or commitment outside your instructions comes back to you. Withdrawing permission means stop.
Sensible contact limits and time between retries. No cold outreach, harassment or repeated calls to wear someone down. The recipient can say no.
You should be able to see what was asked and what happened. Recipients need a way to report misuse, and only the details needed for the task should be shared.
WHERE WE GO FROM HERE
We’re starting small enough to learn from real matters. The bigger ideas have to earn their place.
A personal line for calls, callbacks and follow-ups. Clear updates and a handback when you’re needed.
UK private-beta waitlist openA verified person behind each permission. A practical check, developed with the organisations receiving the calls.
The concept you can try above.Your identity, instructions and history carried between assistants and organisations, with you still in control.
The direction we’re working towards.A LITTLE PROXY. A LOT LESS CHASING.
Join the UK private-beta list. We’ll be in touch when there’s a place for you.
Join the private beta Free to join. No card needed.