Budapest.fm Recorder
Learn how a branded web recorder collects voice submissions with private review, automatic transcription, consent controls, and reporting.
What the Budapest.fm Recorder is
Use the Budapest.fm Recorder to collect spoken submissions from your audience through a branded web recorder on your site or through a direct link. It works in a supported browser on a phone or computer, so contributors do not need to install an app before they can take part.
The recorder lets contributors respond in their own voice, which is often more natural and detailed than a typed form. Your organisation controls the branding, the question being asked, the consent language shown before recording, and the review process after submission.
That makes the recorder suitable for organisations that want to hear directly from customers, readers, visitors, members, residents, guests, or community participants without making anything public by default. Voice collection stays private until your team reviews each submission and decides what happens next.
This page is a product brief for organisations evaluating voice collection. For a broader introduction, see the Voice collection overview.
The contributor journey
The contributor experience is designed to remove setup friction while keeping expectations clear before someone records.
Open the recorder link
Contributors open a recorder page from your website, campaign page, newsletter, social post, QR code, or a direct link. The page presents your branding and the recording experience in one place.
Read the question and consent language
Before recording starts, contributors see the question or topic you want them to respond to, along with the consent language you choose to show. This gives them the information they need before they decide whether to continue.
Allow microphone access
The browser asks for microphone permission when the contributor is ready to record. Once access is allowed, the recorder can capture audio from the device microphone.
Record a response
The contributor records their answer directly in the browser. This keeps the process simple for people using either a phone or a computer.
Listen back before sending
After recording, the contributor can listen back to check that the audio is clear and that the response says what they intended. This helps reduce incomplete or unusable submissions.
Re-record if needed
If the recorder setup offers another attempt, the contributor can record again before submitting. This supports a cleaner final submission without adding editing tools that make the process more complex.
Submit the recording
Once the contributor is satisfied, they submit the recording to your organisation. The submission then moves into private review rather than going public automatically.
The organization experience
Each submission arrives in a private Voice inbox for review by your authorised team. The inbox brings together the recording itself, an automatic transcript created on arrival, source details, the recorded consent state, review status, and team notes so that decisions can be made in context.
That review process is deliberately private. Your team can assess whether the recording is relevant, complete, usable, or suitable for follow-up before deciding what to do with it.
Nothing is published automatically. A person reviews the submission, sees the available context, and decides whether to keep it for internal use, follow up with the contributor, or use it later in an editorial, community, research, or organisational workflow.
Key inbox features include:
- The original audio submission
- Automatic transcription on arrival
- Source details for where the submission came from
- A visible consent record
- Review status tracking
- Team notes for internal decisions
Capabilities
| Capability | What it means |
|---|---|
| Branding | Show your logo, colours, and organisation name so the recorder feels connected to your brand. |
| One clear question | Ask a single focused question or topic to guide stronger, more relevant responses. |
| Consent language | Present your chosen consent language before someone records so expectations are clear in advance. |
| Browser recording | Contributors record in a supported browser on phone or computer without installing an app. |
| Listen-back before submit | Contributors can check their recording before they send it. |
| Re-record option | If configured in the recorder flow, contributors can try again before final submission. |
| Automatic Voice transcription | Each submission is transcribed on arrival to support faster review and internal handling. |
| Private review | Submissions arrive in a private Voice inbox rather than becoming public automatically. |
| Campaign or source attribution | Review where submissions came from, such as a campaign link or referral source. |
| Reporting | Monitor recorder visits, submissions, completion rate, source performance, and activity over time. |
Use cases
- Customer stories and feedback - collect spoken reactions, testimonials, or service feedback in the contributor's own words.
- Reader eyewitness reports and news tips - invite readers to send first-hand audio accounts or leads for editorial review.
- Visitor and guest experiences - gather impressions from travellers, attendees, customers, or venue guests.
- Community memory and oral history - preserve local voices, lived experience, and personal recollections in audio form.
- Member or resident input - hear directly from members, tenants, residents, or supporters on a specific topic.
- Event reactions - capture immediate post-event responses while the experience is still fresh.
- Research interviews - collect remote spoken responses for qualitative research and review them in one inbox.
- Multilingual collection - invite submissions in more than one language when your audience does not share a single language.
Dafado and Magyar Minute are current recorder users.
Analytics and reporting
Recorder reporting helps you understand whether people are reaching the recorder and whether they are completing submissions. The most useful measures are practical ones that show audience response, source performance, and changes in activity over time.
Use recorder visits to see how much traffic the collection page receives. This helps you judge whether distribution is working and whether enough people are reaching the start of the experience.
Use completed submissions to see how many people finished and sent a recording. This gives a direct view of output volume and helps you plan review capacity.
Use completion rate to compare starts with finished submissions. A low completion rate can indicate that the question is unclear, the consent language feels too heavy, or the audience needs a better explanation before they begin.
Use campaign or referral source to understand where responses are coming from. This helps you compare channels such as newsletters, social posts, partner sites, printed QR codes, or direct links.
Use activity over time to spot peaks, slow periods, and response patterns across a campaign or collection period. This helps you decide when to remind audiences, extend a collection window, or shift promotion to a stronger channel.
Illustrative example
- Recorder visits: 1,200
- Completed submissions: 84
- Completion rate: 7%
- Top source: newsletter
- Highest activity: first two days after launch
These figures are an illustrative example only.
Privacy and consent
Show consent language before recording starts so contributors can decide whether to continue on clear terms. The recorder supports a configurable consent step, and the resulting consent state is available with the submission for internal review.
Submissions arrive in a private inbox that authorised team members can review. That supports controlled handling of recordings, transcripts, and notes instead of sending responses straight into a public workflow.
Publication decisions stay deliberate. Your team reviews the submission first, considers the consent record and intended use, and then decides whether anything should be used more widely.
Consent needs depend on how you plan to use the recording and on the requirements that apply in your location. Organisations should define their own consent wording and review process based on their use case.
This section is not legal advice. Consult qualified legal counsel for your jurisdiction before deciding on consent language or use of recorded submissions.
Implementation path
Recorder setup works best as a managed launch with clear editorial, operational, and consent decisions before you invite contributors in.
Discovery call
Start with a discussion of your audience, collection goal, expected submission volume, review workflow, and likely launch channel. This shapes the recorder setup around an actual use case rather than a generic form.
Question and consent design
Define the question, topic, or recording request people will respond to, then agree the consent language that should appear before recording. Clear wording at this stage improves both submission quality and internal confidence during review.
Brand setup
Prepare the organisation name, logo, and colours that will appear in the recorder experience. This keeps the collection flow recognisable and aligned with the environment where contributors first see it.
Embed or link placement
Decide where the recorder will live in the audience journey. Some organisations place it on a campaign or article page, while others distribute a direct recorder link through email, social channels, events, or printed materials.
Testing
Test the recorder flow on the devices and browsers your audience is likely to use. Check microphone access, question clarity, consent display, submission handling, and inbox review so there are no surprises at launch.
Launch
Open the recorder to your intended audience and support the launch with the right distribution plan. A clear invitation usually matters as much as the recording tool itself.
Ongoing review
Review incoming submissions in the Voice inbox, monitor reporting, and refine the collection approach if needed. Teams often improve response quality over time by tightening the question, changing placement, or adjusting outreach.
Pricing approach
Recorder deployments are typically structured around three pricing components. This keeps setup work, ongoing access, and usage-related costs separate so the commercial model can match the organisation's expected volume and workflow.
The first component is one-time implementation. This covers the initial setup work needed to prepare the recorder for your organisation, including configuration and launch preparation.
The second component is recurring workspace access. This covers continued access to the working environment where your team receives and reviews submissions.
The third component is usage based on recording and transcription volume. This reflects how much audio is collected and processed over time, which makes it more suitable for organisations with different collection sizes or seasonal patterns.
Optional custom work can be scoped separately where needed. Examples include campaign design, custom reporting, integration work, and extended retention arrangements.
Early recorder deployments are quoted around the organisation's goals, expected submission volume, and operating needs rather than a fixed one-size-fits-all package.
Recorder pricing is scoped around the number of active recorders, expected recording and transcription volume, team workflow, and retention requirements. You receive the scope and price before setup begins.
Qualification checklist
Use this checklist to decide whether the recorder fits your organisation and workflow.
- You have an audience you want to hear from.
- You have a clear question, topic, or request for contributors.
- You need private review before anything becomes public.
- You want audio and text together for easier internal review.
- You have a team member or team available to review submissions.
- You want branded voice collection without an app requirement.
- You expect value from hearing people in their own voice rather than only through typed forms.
- You want to understand which channels are driving completed submissions.