Put Blip inside your app.Your team never leaves.
Add Blip's recorder to the software your team already lives in, and let your customers report problems on video straight into your support queue. No new tabs, no extra logins.
We'll only email you about early access.
Project SystemProjects
Launch plan Q3 roadmap Website refresh Hiring
Launch plan
On trackWhat's in the plugin
Three things, one install.
Already running
Built into Project System.
Project System is the first app with Blip inside it. Here's what that looks like for its users.
- 1
Record from any project
Record a Blip sits in the top bar, and every project has a Record button. Blip opens in place, with the project already picked.
- 2
Bugs and action items become tasks
Report a bug on video and it's a Blip ticket that Project System also files as a task. Action items from a Blip turn into tasks too, linked back to the moment.
- 3
Project System's rules decide who watches
Project System sends Blip who's on each project, so adding or removing someone changes what they can watch.
Your rules, not ours
Access follows your app.
Blip never learns your rules. Your app runs its own check as each person and tells Blip what they can see, so the answer is always the one your app would give.
In Project System
Mei is on Launch plan and Q3 roadmap.
Added to Q3 roadmap.
In Blip, for Mei
Support tickets
Let your customers show you what's wrong.
Put a Report a problem button on your app or site: a tab on the edge, a circle or a pill, in your colour with your logo. Your customer shows the problem on screen, says what happened, and your team gets a ticket that already has everything it needs.
Payment
Card number
Expiry
Name on card
Pro plan
Monthly$49.00
Total$49.00
No account for your customers
They give a name and email, record and send.
The details come with it
The page they were on, their browser and window size, their steps and what they expected.
They say how bad it is
Major or minor. Only your team can call something a blocker.
Private to your team
Reports have no public link. Only your team can watch them.
Into your own ticket system
Your app files each report and answers with the ticket number, which your customer sees when they send.
Hard to spam
Only the sites you list can use your button, and each visitor can send a few reports an hour.
What your team gets
Everything Blip does, in your app.
No new tab
Blip opens as a small card next to the button they pressed.
No pop-ups
Everything stays in your page. Turn on windows if you want Pause and Stop floating over other apps.
Filed in the right place
Each Blip goes to the project they recorded it from.
Comments, transcripts and views
Every Blip comes with its share page, as it does anywhere.
Tasks from videos
Bug reports and action items can become tasks in your app.
Always current
The plugin loads from Blip, so new features reach your app without a release.
For your developer
Three steps to install.
Or paste one prompt to your AI. It reads Blip's install guide and does all three, then checks its own work. Every call is in the docs.
Add Blip to this app: a Record button (people record a Blip from inside my app) and a Report a problem button (what they send becomes a ticket in my app). Read https://sendablip.com/plugin/v1/INSTALL.md first and follow it step by step. Use the files it links to; don't write your own versions of them. My Blip API key is in the env as BLIP_API_KEY (and BLIP_WEBHOOK_SECRET if I made an app). Never put either in browser code or in the chat. When it's in, run the checks in the guide (GET /api/v1/me and the test webhook) and tell me what they said.
Add the Record button
One script from Blip and one attribute. Your button asks your server for a link and opens Blip's recorder right from the click.
<script src="https://sendablip.com/plugin/v1/recorder.js" async></script>
<button data-blip-record="/api/blip/record"
data-blip-ref="yourapp:project:42">Record a Blip</button>
<!-- React: <BlipRecordButton blipRef="yourapp:project:42" />
from sendablip.com/plugin/v1/blip-react.tsx -->Make the link on your server
Your server asks Blip for a link for this person, with your own id for what it's about. They record without a Blip account, and your API key never reaches the browser.
import { createRequest, requireBlip } from "./blip";
// POST /api/blip/record
const r = await createRequest(requireBlip(), {
ref: `yourapp:project:${project.id}`,
recipient_name: me.name,
expires_in_days: 1,
});
return Response.json({ url: r.ok ? r.data.url : null });Turn reports into tickets
Add the Report a problem button to any page, in your colours. Each report reaches your app as a signed webhook; file it however you like and answer with the ticket number.
<!-- On your app or site -->
<script src="https://sendablip.com/plugin/v1/support.js"
data-token="YOUR_TOKEN" data-color="#0F766E" async></script>
// Your webhook
const w = readWebhook(secret, rawBody, req.headers);
if (w?.type === "ticket.created") {
const t = await tickets.create({
title: w.ticket.title,
body: w.ticket.body, // and page, browser, errors
from: w.reporter.email,
files: w.files, video: w.video,
});
return Response.json({ ticket: { ref: t.number, url: t.url } });
}Webhooks your app can listen for
Signed with your app's secret and retried until your app answers. Pick the ones you want in Settings, Developers.
Recordings and tickets
video.readyA Blip is ready to watchticket.createdA support ticket comes inticket.transcript_readyWhat was said in a recorded ticketticket.assignedA ticket is assignedticket.note_addedYour team adds a noteticket.taggedA ticket's tags changevideo.tasksAction items become taskswebhook.testYour test, to check your route
Blip Reply
reply.invite_readyAn invite is ready for your app to sendreply.openedSomeone opens their linkreply.startedThey answer the first questionreply.completedThey finish, with the reward codereply.taggedYour team tags their answersreply.clip_publishedA clip goes live
Built to be safe in your app
Nothing loads where it shouldn't.
Your sites only
A support button works only on the sites you list. Anywhere else, the card says so and sends nothing.
Short links
Each recording link is made by your server for one person, and runs out when you say: a day is plenty.
Signed webhooks
Every webhook is signed and time-stamped, so your app knows it came from Blip.
Questions
Do my users need a Blip account?
No. Your app makes a link for each person, and they record with just their name. Your own team can record signed in to Blip instead.
Do our customers need an account to report a problem?
No. They give their name and email, record the problem and send it. The video stays private to your team.
Where do the support tickets go?
To your own system. Blip sends each report to your app with the video, the page, the browser and the steps. Your app files it and answers with the ticket number, which your customer sees.
Will it slow my app down?
No. The script is small and loads only when someone presses Record.
Can my app decide who sees each video?
Yes. Your app tells Blip who can see each project, using your own rules, and Blip follows them.
Does it work for Blip Reply too?
Yes. Your app can start Reply invites from its own events, like a purchase, and hear back at every step.
How do we get it?
On the Business or Reply plan, make a key in Settings, Developers, then follow the install guide at sendablip.com/plugin/v1/INSTALL.md, or paste the prompt above to your AI.
Can my AI install it?
Yes. The install guide is written for it: the files to copy, the two routes to add, and two checks it runs to prove it works. You make the key in Blip; it never sees it.
Your app,
with Blip inside.
We'll only email you about early access.