Repeated explanation
Communication and accessibility needs may have to be restated to every new person, even when the wording rarely changes.
MyDisclaimer
An upcoming accessible call-handling proof of concept for people who want to prepare how they communicate, reduce repeated explanations and make deliberate choices during telephone conversations.
Early-stage work. MyDisclaimer is not currently offered as a public service.
The extra work hidden inside a phone call
Some people enter important calls already carrying an additional burden: explaining what they need, choosing when to disclose it, and repeating the same information when the next call begins.
Privacy under pressure
Disclosure decisions can arrive at the hardest point in a conversation, with little time to consider what is necessary or proportionate.
Control in the moment
Busy, stressful or inaccessible calls can make it difficult to introduce prepared information, select a response or record an agreed conversation.
A practical interface for prepared communication
The PoC brings a focused set of call-handling tools into a browser softphone so they can be tested together, with real users and clear operational limits.
Reusable prompts
Prepare clear, personal messages before a call rather than finding the words under pressure.
Configurable actions
Choose an appropriate response for a known context while keeping the final decision with the user.
Trigger rules
Surface a recommendation when call details match conditions the user has set in advance.
Recording controls
Make recording state explicit and test a server-side approach, with local capture only as a labelled fallback.
Simple IVR
Explore pre-agreed caller choices where a short menu can reduce repetition or route the next step.
Useful call history
Retain enough context to understand what happened without turning the interface into a general-purpose contact database.
How the proposed setup works
The browser experience is one part of a managed phone path. Sensitive telephony control stays behind the service boundary.
01 / User
Browser interface
The user prepares preferences, registers the softphone and handles a call in the MyDisclaimer client.
02 / Connection
Secure SIP/WebRTC
Encrypted browser media connects to a compatible SIP service through controlled network infrastructure.
03 / Service
Managed telephony
An enhanced, Asterisk-backed control service can coordinate advanced playback, IVR and recording.
The control service keeps PBX and Asterisk ARI credentials away from the browser while exposing only the actions the PoC needs.
Responsible boundaries from the start
The pilot should test a useful idea without hiding the limits of browser calling or widening the service beyond what can be operated responsibly.
Ordinary mobile calls stay separate
The PoC does not intercept, control or inject audio into calls handled by a phone's native cellular dialler.
Availability is visible
In a pure browser or PWA setup, inbound calls can arrive only while the app is open and registered.
Infrastructure credentials stay protected
PBX and Asterisk ARI credentials remain server-side and are never placed in client code or browser storage.
Routing remains contained
External call forwarding is not included. Call paths must stay within the managed pilot configuration.
Recording cannot be ambiguous
Server-side recording is preferred, recording state must be visible, and any local fallback must be clearly labelled.
Emergency calling is out of scope
The PoC is not an emergency calling service and must not be presented or relied upon as one.
What a pilot needs to discover
The point of the PoC is to learn where this approach helps, where it creates friction, and what would be required for a responsible next stage.
-
01
Usability
Can participants prepare and use communication choices without adding new cognitive or administrative load?
-
02
Reliability
Does the browser and telephony path behave predictably across realistic devices, networks and call conditions?
-
03
Accessibility value
Which parts reduce repetition, improve confidence or support a more equitable conversation, and for whom?
-
04
Service integration
What operational changes would organisations need to recognise and respond well to user-led communication?
-
05
Safeguarding
Are consent, recording, privacy, escalation and support boundaries understood throughout the experience?
A pilot shaped with the right partners
MyDisclaimer needs practical challenge as much as technical delivery. We are interested in partners who can help define a proportionate, useful test.
Funders
Resource the learning
Support discovery, accessible participation, technical delivery and independent evaluation.
Accessibility organisations
Challenge the design
Help frame real needs, inclusive recruitment, safeguards and meaningful measures of value.
Telecom specialists
Strengthen the service path
Bring SIP, WebRTC, Asterisk, security and operational experience to the pilot architecture.
Pilot participants
Ground the work
Test whether the approach fits real communication contexts and identify what must change.
Help shape a careful pilot
If your organisation can fund, challenge, integrate or participate in the MyDisclaimer PoC, we would welcome a focused conversation.