Support plans and limits: Free tickets, seats and services by plan
Support is included in every fewbase plan. Free gives you 30 tickets a calendar month, 1 service and 1 seat; fewbase Pro and fewbase Business raise every one of those numbers — and unlock Pro or Business in every other tool at once. See Billing and plans.
What each plan includes
Section titled “What each plan includes”| Free | fewbase Pro | fewbase Business | |
|---|---|---|---|
| Price | €0 | €9/mo or €90/yr, all tools | €29/mo or €290/yr, all tools |
| Tickets per calendar month | 30 | 500 | 3000 |
| Services | 1 | 5 | 20 |
| Seats | 1 | 3 | 10 |
| Replies, customers | Unlimited | Unlimited | Unlimited |
| Portal page and widget | Included | Included | Included |
| Email notifications to you and to customers | Included | Included | Included |
| Images | Up to 3 per message, 5 MB each | Up to 3 per message, 5 MB each | Up to 3 per message, 5 MB each |
| Auto-close | Included | Included | Included |
| “Powered by fewbase” on the portal | Shown | Shown | Shown |
All the limits above are enforced.
Free gives one service per account: one portal address and one widget, with up to 30 tickets a calendar month and 1 seat — the owner answering alone, with no invite form. Replies and customers are unlimited.
Ticket limit
Section titled “Ticket limit”Only new requests count toward the monthly number — replies, closes and reads don’t touch it. A request sent while Confirm the sender’s email is off counts only when the customer confirms the address by acting on their personal link, so requests typed with other people’s addresses never use up the limit. The month is a calendar month in the owner’s time zone (from their fewbase account), and the count is per service: two services under the same account each get their own 30, 500 or 3000.
When the limit is reached, the portal form and the widget tell the customer the service isn’t accepting requests right now — the same message shown when accepting is switched off in Settings. Existing threads are unaffected: customers keep replying and you keep answering from the inbox.
The owner gets an email at 80% of the month’s number (“Support: 80% of this month’s requests used”) and another when it’s reached (“Support: monthly request limit reached”), each sent once a month. Below 80% there is no email. The inbox shows the same information as a banner — the count and a link to plans from 80%, plus a note that new requests are paused until the 1st once usage reaches 100%. Below 80% the inbox shows nothing.
Appearance
Section titled “Appearance”Position, button text and colour, name and subject fields, the sent-screen
text, the widget’s language, hiding the button on phones and opening it
from a #support link are on every plan. The rest of the
Appearance tab needs Pro or Business:
- Button style, icon, shape, size, distance from the edge, shadow
- Panel corner radius, theme, accent colour
- Form title and subtitle, panel size
- Removing the “Powered by fewbase” line
- Your own trigger button (CSS selector)
On Free these settings show their default value, disabled, with a PRO mark and a link to the plans. If a service on Pro or Business saved any of these and then drops to Free, the values stay in the database — sites just render the default look until the service is Pro or Business again, when the saved values apply automatically.
A seat is used by the owner and by every row in the team, including invitations nobody has accepted yet — not only agents who signed in. Free gives 1 seat, Pro 3, Business 10. See Settings → Team for inviting agents.
Pro and Business
Section titled “Pro and Business”Pro raises the limits to 500 tickets a month, 5 services and 3 seats. Business raises them further to 3000 tickets a month, 20 services and 10 seats. Both are billed as part of the fewbase-wide Pro or Business subscription, not per product.
A new service is created from the service menu at the top of the inbox — + New service. When your plan’s limit of services is reached, the same item opens a page that says so, with a link to the plans. Only services you own count: being an agent in someone else’s service does not use a slot. The plan is shown next to the Support name in the header.
Protection limits
Section titled “Protection limits”These limits exist to keep the portal usable, not to meter the plan:
- Email confirmation. A request from the portal or the widget becomes a ticket only after the sender presses the button in the confirmation email. The link lasts 24 hours and works once.
- Requests per address. No more than 3 unconfirmed or unverified requests per address in one service and no more than 5 across all services within 24 hours. This is the same cap whether Confirm the sender’s email is on (where it counts confirmation emails waiting to be opened, and the form asks to check the inbox first) or off (where it counts tickets carrying the “email not verified” label). See Settings and Requests.
- Spam check. Every request form — portal and widget — carries a Cloudflare Turnstile check, and the server verifies it.
- Rate limits. Sending a request and confirming one are limited to 10 per minute per network address; opening customer pages to 30 per minute per link. The page asks to try again in a minute.
What happens when I go over the ticket limit?
New requests stop, on the portal and the widget alike, until the 1st of the next month — existing conversations keep working. Upgrading to Pro or Business raises the number right away.