Support
Support is the tab for help with Bisbe itself. Ask the way you would ask a person. Your question is answered from our own written pages, with the page it came from. If nothing covers it, a real person on our side replies in the same conversation.
People asking you
Outside your business, asking in. This is the only door they use — they never see the rest of the app. Answer once, then write the answer down so nobody has to ask it twice.
7 at the counter1 waiting on you
- not in this demoCan we hold a size run open while we measure the whole spa team?· Queued for releaseA held run is held on the batch board, so if the batch moves, the ten days move with it — and you hear that from us the same day.
- not in this demoTwelve of the Wave Overshirts on our last order have opened at the side seam. What happens on a whole run?· Waiting on youMaria wrote this down. Word for word: “A seam or a stitch that fails inside a year is ours — replaced, not repaired.” “What’s covered is a rule. What someone bought and when is a record — look it up, never guess it.” So each of those pieces is covered. Two things I won’t answer: what was on your last order is Atlantica’s record, not a procedure — and nothing written down says how a whole run is handled on a wholesale account rather than one garment. That part is with Maria.
- opens hereThe stitching on the Wave Overshirt I bought has come away at the shoulder. Is that covered?· Answered from the manualMaria wrote this down. Word for word: “A seam or a stitch that fails inside a year is ours — replaced, not repaired.” “What’s covered is a rule. What someone bought and when is a record — look it up, never guess it.” So the rule covers you. What I won’t do is tell you your own purchase date or whether your size is on the shelf — that’s Atlantica’s record, not a procedure, and I’ve passed it to the order desk with what I have.
- not in this demoI ordered the wrong size. Can I send it back and swap it?· Answered from the manualMaria wrote this down. Word for word: “Unworn, with the lot ticket still on it, inside twenty-one days — send it back and we exchange it.” “The postage back is yours unless the piece is faulty. A fault is not a change of mind, and it has its own page.” “Money going back onto a card is Maria's call every time. Tell us what happened and she hears it the same day.”
- not in this demoWhat is the smallest first order you will take?· Answered from the manualMaria wrote this down. Word for word: “A first order is thirty-six pieces, across at least two styles. That is the whole of the minimum.” “After that there is no minimum on anything we hold in stock — order six if six is what you need.” “Freight sits outside the minimum. Whether it is included depends on your tier, and the order desk will tell you which you are on.”
- not in this demoHow do we place a reorder ourselves instead of waiting for the rep?· Answered from the manualMaria wrote this down. Word for word: “Send the reorder in here and it lands on the order desk the same hour.” “Piece, colourway, sizes and the ship window you need — all four.” “Anything sent after 4pm island time is next working day.” “Your rep sees it too, so you never have to send it twice.”
- not in this demoCan the linen shirt go in the washing machine?· Answered from the manualMaria wrote this down. Word for word: “Cold wash, inside out, on its own the first time. Nothing we make goes in a hot machine.” “No bleach and no softener. Softener is what flattens the weave on the linen, and it does not come back.”
The rest of the counter
- 1 drafted manual change waiting on your say-so. Read them in Ask, where the exact lines are.
You asking the practice manual
The other direction — and in the practice world it stays inside the practice world: this asks the invented business's own manual, and nobody is paged. It is the real loop on invented records.
Ask the practice manual
You are in the practice world, so this asks the practice manual and nobody is paged. It is the real loop on invented records — reset it whenever you like.
Who’ll answer this
- Your manual, straight awayif it covers it
- No agent of yoursyou haven't set one upYou can connect the agent you already use, and it'll be able to answer from your manual.
- Maria, if nothing else doesit goes to them — no time promised
Works in the live app. Nothing in this demo writes.Answered from what is written down first. If nothing covers it, it goes to Maria — never to a guess.
New here? Your first ten minutes not in this demothe short walk-through of the app, in our own words
Which door is which, how this is built, and what isn’t built yet
Which door is which
- Your customers knock here — outside your business, asking in. This is the only door they use; they never see the rest of the app.
- Your team talks in Rooms — your own channels, one per piece of work. Inside your business; no customer is ever in there.
- You, about Bisbe itself get help here too, from us — Bisbe runs on Bisbe. Your question about the app is answered out of OUR manual, and reaches our team when it is not written down yet. No separate site, no portal.
The other direction — your own customers knocking on your door, answered out of your manual — is the same counter with the channel flipped. It is not switched on: someone with no account at all needs an identity and an abuse posture this does not have yet.
How this is built
For the person who asks what it runs on. What the whole suite is built with, who can see what, and what a program outside it can reach — in plain English.
What it runs on
- Language TypeScript, end to end — the screens, the server code and the checks are all one language. A change that breaks a promise between two of them stops at the compiler rather than in front of a rep.
- Screens React, rendered on the server by Next.js, so a screen is up when a thumb lands on it rather than still deciding. Nothing on this app writes from the browser.
- Server Node.js. Every save runs on the server as an action belonging to the screen that owns it, and each one checks who is asking again before it does anything — not only on the way in.
- Records PostgreSQL, hosted on Supabase, reached with the same AIU sign-in as the rest of the suite. Who may read or write a row is decided by the database itself, row by row, rather than by the screen that happens to be asking.
- Hosting Vercel.
- What gets checked Around 800 automated checks run before anything about this app ships. Separately, every screen is photographed and read back, so a claim about what is on a screen is measured rather than remembered.
- Look and feel The shared AIU design system — the same header, type, theme and material as every other AIU app, so the suite reads as one product.
Who can see what
- One sign-in. The same AIU account opens every app in the suite, and there is no second password anywhere in here.
- Signed in is not the same as let in. Each app is granted to your account separately, and an app you have not been granted is a door that does not open.
- Which rows you may read, and which you may change, is decided by the database itself — row by row, not by the screen that happens to be asking. One business's records stay one business's, and a screen cannot talk its way past that.
- Every action that saves is checked again on the server before it writes, under the permissions of the person who pressed the button.
The services behind every screen
Every capability in here is a service, and every screen you use runs on the same ones. No screen has a private route to the data underneath it. That is what makes it possible to open the same capabilities to your own tools later without building a second product to do it.
- Today
- Nothing here is a public API today. One thing is genuinely open: the connector.
- The connector reaches your written manual and the Ask surface that answers from it — your own assistant, for your account only, set up once in Ask and working on every device you sign in from.
- Inside the product the screens already work this way: nothing talks to an outside system directly, it all goes through one typed layer with the services behind it.
- Where a service is not really wired to anything yet, it refuses when it is called rather than handing back a plausible-looking number. Each one says which it is on its own page.
- 4 of the 7 doors can be reached through the connector today. The other 3 declare no route yet, and each one’s own page says so.
- Planned
- Not built
A service surface for the whole suite — the same capabilities every screen uses, offered to programs you write or buy, under your own account's permissions. - Not built
A connector route for the doors that have none today, so an assistant can reach your channels, your contacts and your customers' questions the way it already reaches your manual. - Not built
The things a service surface needs before anyone outside can be handed one: keys you can issue and revoke yourself, limits, and a readable record of what was called.
- Not built
The longer read — the stack, the parts and access, in about three minutes →
What isn’t built at this counter
- Not built
Being built — Watching a request turn into work needs a read-only projection of the real board — the page promises a projection and forbids a private copy — and that is three columns and a view on a schema no customer can read today. The change is written and waiting on approval; until it is applied there is nothing here to watch, and nothing here pretends there is.
Back to Ask7 conversations at this counter