Overview
MissedCall Respondr is a call-response and follow-up automation platform. It captures incoming call data, lets you define custom response rules, sends automated text/callback replies, tracks follow-ups, and manages your contacts — all from one dashboard.
Built for businesses that never want to miss a lead or client callback, MissedCall Respondr helps you close the loop on every inbound call.
Getting Started
Accessing the App
Open your browser and navigate to:
https://app.missedcallrespondr.com/
Login Credentials
Sign in with the email address and password issued to your account. The password is generated by the system and emailed to you when the account is created, so keep that message.
Logging In
- Visit the app URL above.
- Enter your email address and password.
- Click Sign In.
- You land on the Overview screen.
API Access
All platform resources are also available via the REST API at:
https://app.missedcallrespondr.com/api/v1/
The tenant console is a client of this API. There is no API-key capability on a tenant account: the console has no API-keys screen and the API-key routes were removed, because a key minted there was accepted by no endpoint. Every route the console uses takes your signed-in session instead. Machine access to your own data is not a self-serve feature — ask the platform operator.
Dashboard — the Overview screen
The first screen is the Overview. It summarises what is set up on your account — it is not a traffic report and it has no date-range picker.
Summary Cards
Four counters, each the total number of rows on the matching screen:
| Card | What it counts |
|---|---|
| Response Rules | Response rules defined for this account. |
| Templates | Saved message templates. |
| Contacts | Contacts in the directory. |
| Auto-Responses | Automated responses the platform has sent. |
Your plan & call credits
The Your plan card names the plan this workspace runs on and the allowances it grants — response rules, phone numbers and contacts. Under those figures sits the call-credit line: how many calling credits are left, or, when there are none, a sentence that says a missed call cannot be answered yet and that credits are added by our team rather than from this dashboard (email our contact page and we switch them on). The Plan & Billing screen lists what each plan includes.
One credit pays for one inbound call handled on your MissedCall number, so the credit line is worth a glance when the balance gets low.
When our team moves you onto a plan. If this install cannot take a card, a plan change is made for you by our team after you ask for it — and we email the workspace owner when it happens. That message names the plan you are now on, says plainly that nothing was charged for the change, and points at Plan & Billing so you can see what the plan includes. If it names a plan you did not ask for, reply to that message and we put it right.
Call Log
The Calls screen (the Call Log in the sidebar) lists this account's inbound calls, newest first. It is a plain table with a Refresh button and an Export CSV button.
Table Columns
| Column | Description |
|---|---|
| Caller | The caller's name when the number matches a contact, otherwise the number. |
| Called | The number the caller dialed (yours). |
| When | When the call came in. |
| Disposition | What happened to the call (missed, answered, …). |
| Action | Respond — offered on a missed call. It queues a call-back follow-up (it appears in Follow-ups). |
The table shows the most recent 100 calls; Refresh reloads it from
GET /api/v1/calls.
Export CSV downloads the call log as call-log.csv, one row per
call, with the columns ID, Caller, Called, When, Duration Seconds, Disposition.
Caller follows the table's own rule — the name when one is known, the number otherwise.
The file comes from GET /api/v1/call-logs/export, which reads the same table this
screen lists, so the download cannot disagree with the rows above it; unlike the table it is not
capped at 100 rows. CSV is the only format.
Phone Numbers
Phone Numbers lists the numbers this account holds, read from
GET /api/v1/telnyx/numbers. + Add Number adds one, and the
Release button on a row removes it from the account.
| Column | Description |
|---|---|
| Number | The number itself. |
| Status | active while the account holds the number. |
| Added | When the number was added to the account. |
Adding a Number
+ Add Number takes the number with its country code (for example
+15551234567) and an optional label. How the number is acquired depends on the
account: when the platform holds a Telnyx credential the number is bought on the platform's
Telnyx account, and when the account has connected its own Telnyx key under
Integrations (Pro and Enterprise plans) the number must already be
yours on Telnyx and is registered here. How many an account may hold is the plan's own limit
(Free 1, Pro Monthly 5); at the cap, or when the platform has no Telnyx credential saved, the
server's own message is shown and nothing is added.
Releasing a Number
Release (confirmation required) removes the number from the account and frees the plan slot, so it leaves this list and can be added back later. The platform operator can also provision and release numbers for an account.
Response Rules
Response Rules are the heart of MissedCall Respondr. They define when and how the system automatically replies to an incoming call.
Creating a Rule
- Navigate to Response Rules in the sidebar.
- Click + Add Rule.
- Fill in the rule fields (see table below).
- Click Add (or Save when editing). From that moment the rule is evaluated on every inbound call.
| Field | Description |
|---|---|
| Name | A label to identify the rule (e.g. "After-Hours Auto SMS"). |
| Trigger | When the rule fires: All missed calls, Specific numbers, Time of day, or Day of week. One trigger per rule. |
| Trigger details | Whatever the trigger needs — the caller numbers (Specific numbers, one per line), the From/To window (Time of day), or the days (Day of week). |
| Action | SMS (text the caller back) or Callback (queue a return call for you in Follow-ups, due in an hour). |
| Message | For an SMS rule, the text to send. It goes out exactly as typed — no placeholders are substituted. |
| Priority | Rules are evaluated in priority order (lowest number first; the default is 100). |
| Enabled | Toggle the rule on/off without deleting it. |
Rule Evaluation Order
Every inbound call walks your enabled rules in priority order (lowest number first, oldest first where two rules share a priority). The first rule whose trigger matches fires, its action runs, and the rest are skipped for that call. If no rule matches, the call is logged and nothing is sent.
What an SMS Needs
A text leaves through Telnyx, from the number the caller dialed. On a number the platform provides, the message goes out on the platform's own Telnyx account, so there is nothing for you to enter. A Pro or Enterprise account that has connected its own Telnyx key under Integrations sends on that account instead. If this installation has no Telnyx account saved yet, a rule still fires and is logged, but the Messages screen stays empty because nothing was attempted — write to us from our contact page and our team switches it on. Queued, sent, delivered and failed on the Messages screen are always the provider's own answer.
Testing a Rule Before a Caller Rings
Above the rule list there is a Test a caller box. Type a phone number, press Test this number, and the screen answers the two questions you cannot otherwise check without waiting for a real missed call: would any of my rules answer this caller right now, and what would the caller actually receive. It reads your rules exactly the way an inbound call does — the same priority order, the same triggers, the same current time — and reports the first rule that matches, together with the text it would send (for a Callback rule it tells you a callback would be queued instead). Testing writes nothing: no call appears in the Call Log, no message is queued, no text leaves the platform, so you can press it as often as you like. A number that no rule answers is worth knowing about too — the box says so in plain words, and tells you whether that is because you have no enabled rules yet or because every rule you have is a time-of-day or day-of-week rule sitting outside its window.
Managing Rules
- Edit — click Edit on any rule row.
- Delete — click Delete (confirmation required).
- Re-order — change the Priority number; the list is shown in evaluation order, so what you see is the order the calls are checked in.
Name: "Weekend Auto-Reply"
Trigger: Day of week — Sat, Sun
Action: SMS — "Thanks for calling. We're closed for the weekend and will call you back on Monday."
Priority: 10
Follow-ups
Follow-ups is the call-back queue. Rows arrive on their own: the Respond button on a missed call schedules a call-back and a Callback response rule queues one automatically. You can also schedule one by hand with + New Follow-up, close it, or delete it.
What the Screen Shows
| Column | Description |
|---|---|
| Call | The call the follow-up was raised for — the caller and when it came in. Every follow-up is attached to one of your calls. |
| Scheduled | When the call-back is due. |
| Status | The task's state as the server stores it — pending while the call-back is still due, completed once it is closed. |
The list is read from GET /api/v1/follow-ups.
Managing Follow-ups
- + New Follow-up — pick one of your calls, a type (the app's own value is
call_back), the due date and time, and optional notes (POST /api/v1/follow-ups). A follow-up is always attached to a call (call_idis a required foreign key), so the button stays off until the account has at least one call. - Mark done — closes a follow-up (
PUT /api/v1/follow-ups/:idwith statuscompletedplus the completion time). - Delete — removes it (confirmation required).
There is no status filter, no search box and no Assigned To field: the list is every follow-up on the account.
Contacts
Contacts is the directory of the people this account talks to. Each row shows a name, phone and email.
Searching
The search box searches on the server as you type
(GET /api/v1/contacts/search?q=) across name, phone and email. Clearing it returns
the full list, and Refresh reloads it.
Custom Fields
Custom fields store extra per-contact data. The button shows how many fields are defined and opens a panel where you can:
- Add a field — a name, a type (
text,number,dateorboolean) and an order. - Delete a field — its per-contact values go with it.
- Fill in values — once at least one field exists, each row gets a
Fields button that opens that contact's values and saves them with
PUT /api/v1/contacts/:id/fields/:field_id.
Adding and Editing Contacts
- + New Contact — name and phone are required; email, company, tags (comma
separated) and notes are optional (
POST /api/v1/contacts). - Edit — reopens the row in the same form and saves with
PUT /api/v1/contacts/:id. Emptying an optional box clears that field. - Delete — removes the contact and its custom-field values
(
DELETE /api/v1/contacts/:id, confirmation required).
Exporting Contacts
Export CSV on the Contacts screen downloads the whole directory as
contacts-YYYY-MM-DD.csv — every contact on the account, not just the 100 rows the
table renders. Each line carries Name, Phone, Email, Company, Tags, Created; tags are
written separated by semicolons, and any value holding a comma or a quote is quoted so the file
opens cleanly in a spreadsheet. It is the same data the table lists, CSV is the only format, and
the download comes from GET /api/v1/contacts/export, which needs a signed-in session.
A duplicate email inside the same account is refused by the server, which shows its own message. There is still no contact detail page — clicking a row does nothing, and the row's Fields button opens the custom-field values. Contacts are not created automatically from inbound calls; a new caller reaches your CRM through the CoreSwift integration (Integrations), which captures every missed call as a lead.
Lists
Lists is a set of named groups of your leads. Every campaign keeps a list of its own: the moment a lead carries that campaign's tag it joins the campaign's list automatically, so the Lists screen is where you see everyone one campaign has collected.
The table shows each list with how many people are in it and where it came from — Campaign for one the system keeps for a campaign, Your own for one you made. Press View leads to open it. Inside a list:
- Remove beside a person takes them off that list only. They stay in your account and in Contacts — a list is a grouping, not a second copy of your contacts.
- Add a lead puts someone back on the list; the picker reads your current leads each time it opens, so a lead created a minute ago is already there.
- Rename changes the list's name. Everyone already in it stays in it.
- Delete list removes a list you made yourself. The people in it stay in your account and in Contacts. A campaign's own list has no Delete control — the campaign manages that one, and it comes back the next time the campaign collects someone.
- + New list makes a list of your own with a name and an optional description, for grouping people the way you work rather than the way a campaign does.
Calendar
Calendar is your own list of appointments, callbacks and reminders for this workspace. Nothing is sent to a caller from it: an event is a note to you, and it stays inside your account.
Press + New event, give it a title, pick the date and time, choose a type (call, callback, appointment, reminder or other) and add a note if you want one. The screen keeps two tables — Upcoming and Already passed — so a callback you have not made yet stays at the top and an old one does not clutter it. Edit changes an event's title, time, type or note; Delete removes it.
The calendar is part of the Enterprise plan. On a plan without it the screen still opens and says so in the app's own words, with a link to the plans — no event is written and nothing is changed.
Tickets
Tickets is the support-ticket list, read from GET /api/v1/tickets.
Each row shows a subject, a status and a priority.
- + New Ticket — creates a ticket with a subject, a status (Open, In Progress, Resolved, Closed) and a priority (Low, Medium, High, Urgent).
- Edit — reopens a ticket to change its subject, status or priority.
- Open — shows the whole conversation on that ticket (who said what, and when) and gives you a box to answer in. Your answer is stored on the ticket, shown on the customer's own dashboard, and emailed to the workspace's address, so a request filed from Plan & Billing is answered instead of sitting in a list.
Message Templates
Message Templates are saved message texts you keep for reuse. A template is a library entry and nothing more: nothing sends one automatically, and a response rule carries its own Message text. Copy the wording from a template into the rule's Message field when you want to reuse it.
No Variable Substitution
Whatever you type is what the caller receives. {{name}},
{{company}} and the like are not replaced — a rule that sends
Hi {{name}} texts the caller the literal words. Write the message you want them to
read.
Creating a Template
- Go to Message Templates → + Add Template.
- Enter a name (e.g. "After-Hours SMS").
- Write the message body.
- Click Add. It is kept in this list for you to copy from.
Sorry we missed your call! We're on it and will ring you back shortly.
Editing & Deleting
Templates can be edited or deleted from the same list. Deleting a template does not change any rule — rules hold their own message text and never reference a template.
Messages
The Messages tab is the outbound text log and the place you send a text by hand. + Send Message opens a form pre-filled with a number this account holds as the From number; enter the recipient and the text and press Send. The message is transmitted from your own Telnyx number, and the row records what the provider reports — nothing is marked sent or delivered that the provider did not confirm.
What each status means
| Status | What happened |
|---|---|
| queued | Telnyx accepted the message. It has not been handed to the recipient's carrier yet. |
| sent | The carrier took the message. The Sent column shows when Telnyx reported this. |
| delivered | The recipient's network confirmed delivery. The Delivered column shows when Telnyx reported this. |
| failed | The provider refused the message or the carrier reported a failure. The reason Telnyx gave is shown in a dialog when you send; the attempt stays in the log as failed. |
| logged | A message recorded as received (inbound). Nothing is transmitted for these. |
The From number must be a number this account holds — see the Phone Numbers tab in the app. If this installation has no Telnyx account saved yet, sending answers "Text delivery is not configured" and nothing is recorded — write to us from our contact page and our team switches it on for you.
Integrations
Integrations is the provider catalogue for this account. Each card shows a status
badge — Connected or Not connected — and the controls that apply
to it. The catalogue is read live from
GET /api/v1/available-providers, so a provider added on the platform appears here
without a console release.
Available Providers
| Provider | Purpose |
|---|---|
| CoreSwift CRM | Push leads into CoreSwift CRM. Pinned first as Recommended, and the integration every captured call flows into. |
| Telnyx | Bring your own Telnyx account (BYOK): calls, SMS and number management. |
| Twilio | Bring your own Twilio account (BYOK): calls, SMS and number management. |
| Mailgun, SendGrid, Sendiio | Transactional and campaign email delivery. |
| OpenAI, DeepSeek | AI models for content generation. |
| Nexweave | Personalized video/image generation. |
| SAM.gov | Federal contracting opportunities. |
Connecting a Provider
- Paste the provider's API key into the field on its card.
- Click Connect. A provider that can use another endpoint also shows an optional Base URL field.
- Click Test connection to run the live probe. CoreSwift is probed against the hub and reports whether the key was accepted; for the other providers the platform answers that no live test is available yet.
- Click Disconnect to remove the stored key.
Once CoreSwift is connected its card also shows the hub URL and a Push a lead to CoreSwift now form, which runs the same push the automatic capture path uses for a lead you captured by hand.
Profile & Account
The Profile screen (the last item in the sidebar) holds your own account details. There is no separate "Settings" page.
Your Details
- Picture — Upload picture (or Change picture) takes a PNG, JPEG, GIF or WebP up to 2 MB and shows it in the console header; Remove picture puts the initials back. One picture per account, so a new upload replaces the old one.
- Name — the name in the console header and in the messages this app sends you.
- Company — optional; clear it when there is nothing to show.
- Username — optional short handle for your account; clear it to remove it.
- Level — the plan this workspace is actually on, read from the plan itself (Plans & Billing shows the allowance and the upgrade path).
- Email — the address you sign in with. It is not edited in the field above; use the Sign-in email card below to move it.
Changes are saved with Save changes (PUT /api/v1/auth/profile);
the screen confirms when they are stored, and a refusal appears in place with its reason.
Moving your sign-in email
The Sign-in email card shows the address on file. Enter the new one and press Send confirmation link: a confirmation goes to the NEW address and your current address keeps working until that link is opened, so a typo cannot lock you out.
Change Password
Enter your current password and a new one (at least 8 characters) and click
Update password (PUT /api/v1/auth/password).
Email Branding
Your account can put its own logo, display name and colour at the top of every transactional email this app sends — the welcome / login-credentials mail, purchase confirmations and password resets. Open the 🎨 Email Branding tab in the console (it sits beside Site Config) and set:
- Brand display name — up to 60 characters, printed above the message.
- Brand colour — a hex colour such as
#4f46e5; it draws the rule under your logo. - Logo — upload a PNG, JPEG, WebP or GIF up to 2 MB. Once one is set the upload button becomes Replace logo and a Remove logo button appears.
Below the logo and name fields, the Company signature block holds five plain fields — full name, job title, company, phone and a line — that print under your logo on every message this workspace sends. Leave them blank to send without one. Each mailbox can instead write its own signature (or send without one) from the inbox's compose screen, so the workspace default here is just the fallback every new address starts from.
Click Save branding. The logo is served from your account's own public URL
(GET /api/v1/branding/logo/{tenant_id}), which is what lets the recipient's mail app
display it. Until you set a name or a logo nothing changes — every message keeps the
MissedCall look, because branding is per account, not per app.
Under the fields the tab shows the actual email your account sends — not a drawing of it. It is the message your sender builds from the branding you have saved: the subject line, then the logo, display name and colour rule exactly as a recipient opens them. Press Save branding (or upload or remove a logo) and the tab re-reads the message, so what you see is what leaves the building; Refresh re-reads it on demand. Nothing is mailed and nothing is stored by this preview.
Under that preview, Send me a preview email sends the same sample to your own account address. The request names no recipient, so the button can never be used to mail anybody else. Save your branding first: what arrives is exactly what the next real email from your account will look like in an inbox. The line under the button is the server's own answer and says plainly when nothing was sent — for example when the account's address is on a reserved test domain that cannot receive mail.
Your team
A workspace can have more than one login. Open the 🤝 Your team tab in the console to see everyone who can sign in to this account, what access each of them has, and how many seats your plan allows. The person who created the workspace is labelled Owner; anyone added later is a Member.
- Add someone — type their name and email address and press Add them. Their own login is created and an email with their first password goes to that address. Nobody has to share your password, and everything they do is inside this same workspace.
- Remove someone — press Remove on their row. Their login stops working immediately; the calls, contacts and settings stay with the workspace.
- The Owner row cannot be removed here, and you cannot remove yourself — a workspace always keeps one person who can get back in.
Only the Owner and anyone the platform team has made a Company admin can add or remove people; everyone else sees the list and a line saying who to ask. The line under the form is the server's own answer: it tells you when the password email actually left, and when it did not (for instance an address on a reserved test domain that cannot receive mail) it says so instead of claiming a send. If a colleague never receives their password, use Forgot your password? on the sign-in page once mail delivery is confirmed, or ask the platform team to send a reset from the operator console.
Workspaces
A workspace is a separate drawer inside this business account — a client, a location, or a brand you run from the same login. Your plan says how many you may have, and exactly one is the default that opens when you sign in.
The 🗂️ button at the top of the dashboard, beside your workspace’s name, is the quickest way to move around. Open it to Switch to another workspace — the screen reloads signed into that one — or to Add a new one. The full list and the same controls also live on the 🗂️ Workspaces tab in the sidebar.
- Switch — move this session to a different workspace. Your calls, contacts and settings follow the workspace, never your login.
- Add — create a workspace with a name your team will recognise.
- Rename — change a workspace’s name.
- Make default — choose the workspace that opens on sign-in.
- Delete — remove a workspace. The account always keeps at least one, and you cannot delete the workspace you are signed into — switch away first.
The Owner and Company admin see all five controls; a Member sees Switch and Add only. The server enforces the same rule, so a member can never rename or delete a workspace.
MCP — connect an AI tool
MCP in the app's navigation (directly above Profile) connects an AI assistant — Claude, Cursor, or your own agent — to this account. It can read only: there is no tool that changes, deletes or sends anything, and every answer is limited to your own workspace.
The screen shows the endpoint (https://hooks.swiftsoftware.net/mcp) and your
account’s API key, which is created together with your account. Reveal asks
for your password before it shows the key, and every reveal is recorded. Copy
puts the key on your clipboard, and Regenerate replaces it — the old key
stops working the moment the new one is issued, so any AI client still using it must be given the
new key.
The Connect block shows the exact config to paste into Claude Desktop
(claude_desktop_config.json) or Cursor (.cursor/mcp.json). Treat the key
like a password: anyone holding it can read your account, so regenerate it if you think it has
been shared by mistake.
📬 Inbox
The Inbox screen holds your own addresses on your own domain, the newest mail that reached them, and the search for that list. Add the domain you already own, press Show records, paste them at your DNS provider, then press Check again until the domain reads Receiving — mail cannot arrive before that. Create the addresses you want on it, within what your plan sells.
Above Recent mail there is a Search subject, sender or text box: type part of a subject, an address or a phrase from the opening of the message and the list narrows as you type (press Enter to search at once). Capitals do not matter. When nothing matches, the table says No mail matches “…” with a Clear the search button, so a filtered list never looks like an empty inbox; Clear search beside the box restores the list. Reading and answering the whole thread happens in the mail client at inbox.missedcallrespondr.com, which is the same account.
💳 Plan & Billing
The Plan & Billing tab shows the plan this workspace is on right now (the blue badge under Your current plan) and every plan this install sells, with its monthly price and what it includes. Press Upgrade to … on the plan you want: checkout is hosted by the payment provider the install is connected to, so no card details are entered on this site. A plan already on your account reads Your plan, and the free tier reads Included.
If self-serve checkout is not open on this install yet, that same press tells you plainly that nothing was charged and files the request with our team for you — there is no second button to find (a Request the … plan button appears only if sending failed, and pressing it retries). The team make the switch by hand — and you are emailed a receipt for it straight away, naming the plan you asked for and saying that nothing has been charged, so you have a record of what you asked and when. The request then appears under Your plan requests on the same screen with its live state (open, in progress, resolved or closed), and when our team answers you are emailed that answer too.
A request our team has not acted on yet can be taken back: press Withdraw on its row under Your plan requests and confirm. Nothing was charged, so nothing is refunded — the request simply leaves your list and you can ask again whenever you like. Withdraw is offered only while the plan is still off your account and the request is neither resolved nor closed, so once our team has answered, that row is the record.
Frequently Asked Questions
How does MissedCall Respondr receive call data?
Your VoIP provider (Telnyx) sends webhooks to MissedCall Respondr's API. Configure the webhook URL
from your provider's dashboard to point to
https://app.missedcallrespondr.com/api/v1/telnyx/webhook. That one public URL carries
both the call events (which raise the Call Log entry and run your Response Rules) and the message
delivery events (which set a text's Sent/Delivered times). The platform answers the call and plays
no prompt — it collects no keypad input — so the only thing a caller ever receives is what your
Response Rules arrange: a text back, or a callback for you on the Follow-ups screen.
Can I have multiple response rules active at the same time?
Yes. Rules are evaluated by priority. Only the first matching rule fires per call. You can keep as many rules as your plan allows, each with its own trigger and priority.
What happens if no rule matches a call?
The call is still logged on the Calls screen, but no automated response is sent. You can handle it from that row with Respond, which queues a call-back follow-up.
Are message templates required for SMS responses?
No. Type your message straight into the rule's Message field. Message Templates are a separate library you keep for reuse — a rule never references one, so copy the wording in if you want to use it.
How do I export my call data?
Open the Calls screen and click Export CSV. The file
call-log.csv holds every call on the account — not just the 100 the table renders —
with the columns ID, Caller, Called, When, Duration Seconds, Disposition. It is the
same data the table lists, and CSV is the only format.
How do I export my contacts?
Open the Contacts screen and click Export CSV. The file
contacts-YYYY-MM-DD.csv holds every contact on the account — not just the rows the
table is showing — with the columns Name, Phone, Email, Company, Tags, Created.
What variable syntax does the app support?
None for the text a rule sends. Messages and templates are sent exactly as typed —
{{name}}, {{company}} and the other double-curly-brace forms are not
replaced, so write the finished sentence you want the caller to read. (The app's own account
emails — welcome, password reset, purchase — do fill in their own fields; that does not apply to
the text a Response Rule sends.)
How do I reset my password?
On the login page, click "Forgot Password?" and enter your email address. You'll receive a password reset link. You can also change your password under Profile → Change password while logged in.
Someone else may be signed in to my account — how do I get them out?
Open Profile and press Sign out other devices in the Sign out of every other device card. Every other signed-in device is signed out at its next action, and the screen you pressed it from stays signed in — you do not have to change your password to do this. Use it when a phone was sold, a laptop was shared, or a session is one you do not recognise. Changing your password also ends every other session, as it always has.
Is there a mobile app?
The MissedCall Respondr web app is fully responsive and works on mobile browsers. There is no native iOS/Android app at this time.
How do I contact support?
Send us a message from our contact page.
🔗 Referrals & Affiliates
MissedCall Respondr does not run its own affiliate programme. The affiliate
system lives in FunnelSwift; this app only connects to it, over two outbound
x-internal-key wires, and keeps no affiliate store of its own.
What This App Sends
| When | What leaves this app |
|---|---|
| An account moves to a paid plan | A plan-upgrade event, so a referred customer's upgrade can be credited to the referrer. |
| A checkout completes with referral details | A conversion event, so the referral is recorded. |
What This App Does Not Do
- There is no affiliate panel in this app's console — there is nothing to configure here.
- No affiliate products, commission rates or prices are stored in this app. The catalogue belongs to FunnelSwift.
- Nothing in this app tracks clicks or sets a cookie.
How To Get A Link
Ask your account manager, then create and manage your affiliate links in the FunnelSwift affiliate portal. Commission rates, conversions and payouts are all handled there.
Provisioning — a FunnelSwift tag can create a free account here
A lead captured in FunnelSwift can be tagged with MissedCall Respondr — Free. When this app's provisioning switch is on, that tag creates a real, log-in-able free account for the business here: its own workspace, an owner login whose password is emailed to the contact address, and a plan row they can upgrade from.
What happens when it is ON
- A tagged lead gets a real account here on the free plan — not just a contact record.
- The new owner is emailed their login details by MissedCall Respondr.
- Tagging the same lead twice does not create a duplicate account — the second attempt is recognised by email and ignored.
What happens when it is OFF
The tagged lead is still recorded as a contact, so nothing is lost, but no account is created and no login email is sent.
Where the switch is
Operators turn it on or off in this app's admin console, under Create free accounts from tags.
MissedCall Respondr — Built by SwiftSoftware
© 2026 SwiftSoftware. All rights reserved.