viber.pics
Your client draws on the screenshot. You get one thread to answer.
Every client gets an inbox of their own at client.viber.pics. They mark up a page or drop a file — no account, no app to install — and it lands as a numbered item with the conversation attached. You reply where the note is, mark it handled, and move on. Your AI agent can work the queue too.
10 credits a month per workspace, paid from the one Sippis balance you use in every Sippis app. Nothing to pay for the people sending you feedback.
Feedback arrives everywhere except where you fix it
A WhatsApp photo of a laptop screen. A forwarded email with "see attached". A voice note. By the time you sit down to work, you are reconstructing what was meant.
Before
Five channels, no numbering, no record of what was already fixed. Every "did you see my message?" costs you a context switch.
With viber.pics
One address per client. Every note pinned to the pixel it is about, numbered, threaded, and marked handled when it is done — so the workspace is the record.
Two inboxes in every workspace
Both live on the workspace's own address, and both take feedback from people who have nothing to install and no account to create — an invite link is enough, on a phone or a laptop.
Screenshots
They grab the page, draw on what is wrong, and type the note next to it. You get the image, the marks and the note as one item in the batch — up to ten items a batch, each with its own thread.
<workspace>.viber.pics/ss
Files
A logo, a signed PDF, a short video — whatever they have, each with a line saying what you are meant to do with it. A page a client sends arrives as a download, never as a page: nothing they upload can run on your address.
<workspace>.viber.pics/sf
How it works
Four steps, and only the first one is yours to set up.
- Make a workspace One client, one workspace: it gets
<name>.viber.pics, its two inboxes and its own settings. The first period is charged to your Sippis balance and it is live at once. - Send an invite link Scoped to one of the client's projects or to a single batch, for a person or for an AI agent, with an expiry if you want one. Rotate it and every copy dies.
- They mark it up and send Screenshots with drawings and a note on each, or files with instructions. It lands as a numbered batch and you are mailed once, not once per keystroke.
- Answer in the thread, mark it handled Reply next to the item, attach a revised screenshot, close the thread. New findings go in a new batch, so old ones stay finished.
Hand the inbox to your AI agent
Every grant can be issued for a person or for an agent. The agent form is a ready-made prompt: paste it into the coding agent you already use and it works the queue over plain HTTPS and JSON, with a key that can read, reply and mark done — and nothing else.
- Scoped, not global. A key covers one project or one batch. It can never delete a batch, mint another key, or see a batch it was not given.
- The prompt is generated for you. One copy button per key. It tells the agent what to list, what to read, where to reply and when to report back.
- Revisions land in the thread. The agent attaches its new screenshot next to the note it answers, and marks the batch done with a summary of what it changed and what it skipped.
- You keep the last word. Rotate a key and every copied prompt stops working that second. Nothing in the agent's hands can spend a credit or change a setting.
You have access to the feedback inbox for Acme Shop at https://acme.viber.pics
Access key: •••••••••••••••• — send it on every request as header "X-Viber-Key: …"
1. GET /ss?api=list and /sf?api=list → batches; work on every batch with handled=false.
2. GET /ss?api=threads&since=… → messages posted since then; answer each open thread.
3. For a batch: GET ?api=batch&id=… → the notes; GET ?api=file&id=…&file=… → the bytes.
4. Act on every comment. Reply where the comment is: POST {"action":"comment", …}
5. When a batch is done: POST {"action":"done", "reply":"what you changed / skipped and why"}
An excerpt of the prompt a project-scoped agent key produces. The full text is the only thing the agent needs.
Everything a client inbox needs, nothing it does not
Built from the feedback tool sippis.com uses with its own clients, then made multi-tenant. The features are the ones that turned out to matter.
One address per client
Each workspace lives on its own subdomain with its own inboxes, keys, settings and bill. Nothing is shared between two workspaces, not even a directory.
Invite links, not accounts
Reviewers and submitters get a link scoped to a project or a batch, with an optional expiry. Revoke, rotate or delete it in one click; the record of what they sent stays.
A thread on every item
Each screenshot or file carries its own conversation, plus one for the batch as a whole. Either side can close a thread; a new message reopens it.
Mail that does not flood
One message per batch, per person, per ten minutes — with who wrote what and a link straight to it. An agent's mail carries its prompt, ready to paste.
Your own sender
Point a workspace, or a single client project, at your SMTP server and the mail comes from your domain. Leave it blank and it comes from ours.
A second pair of hands
Name one more Sippis user as a workspace's admin. They get full rights on that workspace and no access to your billing.
Storage you can see
A bar on the workspace page shows what is used. Add a block when you need it, drop it when you do not; a full workspace stops taking uploads, never conversations.
Private by construction
Uploads are identified by their bytes, not their name, and anything that could render as markup is sent as a download instead. Keys never appear in logs or mail beyond the link that is the grant.
What it costs
Per workspace, in Sippis credits — the balance you top up once at Sippis and spend in every Sippis app. No card on this site, no per-seat pricing, and no charge for the people sending you feedback.
Monthly
Per workspace. Cancel any time; it runs to the end of the period you paid.
Annual
24 credits less than paying monthly.
Per workspace, charged once a year.
- Both inboxes, screenshots and files
- Unlimited invite links and agent keys
- Unlimited reviewers, no accounts needed
- Threads, notifications and your own SMTP
- One extra admin per workspace
- Your own
name.viber.picsaddress
Storage. Every workspace holds 100 MB of screenshots and files. Need more: blocks of 100 MB for 5 credits / month, added and dropped when you like.
If a payment fails. The workspace keeps working for 30 days. After that it is suspended — everything already in it stays readable, new uploads stop. A suspended workspace is deleted 60 days later, and we mail you 7 days before that happens. Top up at any point and the next daily check brings it back.
Questions people ask
Do the people sending feedback need an account?
No. An invite link is all they need, and it works on a phone. The link carries the name and email you gave it when you made it, so you know who wrote what and they get a mail when you reply.
What is a Sippis credit?
The one balance you top up at sippis.com and spend across every Sippis app, this one included. viber.pics never sees your card and never asks for it; the "Buy credits" button takes you to Sippis and brings you back.
Can I run several clients under one account?
Yes — that is the point. One workspace per client, each on its own subdomain, each billed on its own, all listed on one page under your account.
Can my AI agent really use it?
Yes. Issue a key in its agent form and copy the prompt it produces. The agent lists the open batches, reads every screenshot and note, replies in the thread with a revised screenshot when it has one, and marks the batch done. It cannot delete anything, mint keys, or touch billing.
What happens to my data if I stop paying?
Nothing sudden. You get 30 days of grace, then the workspace is suspended but still readable, and only 60 days after that is it deleted — with a warning mail 7 days before. Top up at any point and the next daily check brings it back.
Where does my data live?
On our servers, in a directory that belongs to that one workspace and is reachable only through that workspace's own address and keys. Nothing is shared between workspaces, and nothing a client uploads is ever served as a page.
Start with one client
Sign in with your Sippis account, name the workspace, and send the first invite link in the time it takes to read this page.