What is new in OtterFront.

Your records are walled off by the database itself

Every signed-in request now runs under database rules that only let it see and change your own business's records. The app already filtered every query by business; this is a second lock underneath it, so a mistake in one query cannot show one business another's customers.

A privacy page

otterfront.com/privacy says what we collect, why, which companies help us run the service, and how to have your data deleted. It is linked from the footer and from every form that asks for your details.

Easier to use with a keyboard or a screen reader

Public pages open with a skip link that jumps past the menu, faint text is darker and easier to read, and the early access form now tells a screen reader whether your signup went through.

One address for the whole product

otterfront.com is the front page when you are signed out and the app when you are signed in. Signing in, signing up and everything you do afterwards happen on the same address, so there is no second hostname to remember or to bookmark by accident.

An embedded quote shows the tax you will be billed

Quotes fetched from your own site now work out sales tax from the customer's service address, the same way the hosted booking page and the final charge always did. A business pricing tax by ZIP code was seeing zero tax on an embedded quote and the real amount on the booking.

Set a tax rate for every ZIP code you serve

Booking settings has a per-ZIP tax table. Enter the rate for each ZIP in your service area and the quote uses the one that matches the address. Rates are held precisely enough for the fractional percentages real jurisdictions charge.

The quote says when tax is an estimate

A customer booking from a ZIP you have not set a rate for sees your default rate and a note saying the final tax is confirmed on the receipt.

Sales tax comes from the service address

Tax is worked out from where the job happens, not from where your office is. In most states that is the law, and across one metro area the difference runs to nearly two points.

A settings area

Settings is a place now, with a page per destination and a line saying what is behind each one. Members, booking page, services, providers and forms were reachable only as unlabelled links in the sidebar before this.

Rename your organization

The name you gave your business at signup is no longer permanent. The web address it was given does not change, so nothing you have already shared breaks.

Claim your own booking domain

Point a domain of your own, like book.yourbusiness.com, at OtterFront and claim it from Settings. It opens straight onto your booking page. Your booking link keeps working either way.

Your own profile

Change your display name and your password from Settings, Your profile. Changing a password signs out every other device and keeps the one you are on.

The booking page stops pointing customers at nobody

Before card payments are switched on, the booking page invites customers to get in touch. It now names your support email or phone only when you have set one, instead of printing an empty sentence and a dead link.

OtterFront looks like itself

The app, the dashboard chart, the browser tab icon, the link preview card and the footer on every email now carry the same mark and the same colour.

Your booking domain opens on your booking page

A domain you have claimed serves your booking page at its root, so the address you print on a van is book.yourbusiness.com and nothing else. The long booking link stays valid.

A neutral page while a domain is still being set up

A domain pointed at OtterFront before anyone has claimed it shows a plain page telling the visitor to contact the business directly. It carries no OtterFront branding, because it is sitting on your brand's domain.

Early access is open

otterfront.com explains what the product does and takes your name for the list. One email when signup opens, and nothing else.

Sign-in and sign-up on brand

The screens you meet before you have an account look like the rest of the product rather than like a scaffold.

A booking page customers can finish

A public page on your own link where a customer picks the job, sees the price, chooses a real arrival window and saves a card. Nothing about it is a form that emails you a request.

Services priced the way you price them

Base price, variants, add-ons, recurring frequencies and a per-job checklist. The quote the customer sees is the one you set, worked out on the server so it cannot be edited in a browser.

Availability that will not oversell you

Arrival windows, how many jobs you can staff per window, lead time, how far ahead you take bookings, the ZIP codes you serve and your blackout dates. A slot you cannot cover is never offered.

Dispatch by private link

Assign a provider and they get their own link with the job, the checklist and the address. No login, no app, no seat to pay for, and the customer's email address is never shown to them.

The card is charged after the work

The card saved at booking is charged when the provider marks the visit complete, for what happened rather than what was promised. A declined card asks the customer to update it and the job stays complete.

Recurring visits that book themselves

Finish a visit on a weekly or fortnightly plan and the next one is created, with the same provider, the same window and the recurring price. A blackout date rolls it to the next day you work.

Customers reschedule and cancel themselves

Every confirmation carries a link where the customer can move the visit, cancel it or update their card. Your late-change policy is applied by the page instead of argued about on the phone.

Payouts grouped by provider and week

Every completed job rolls up per provider per week, so paying the crew is reading a number rather than rebuilding it in a spreadsheet.

Booking emails that look like your business

Confirmations, reminders, receipts and job assignments carry your name, your logo and your support address. Reminders go out the day before to the customer and the provider.

Your own Stripe account

Your Stripe keys are stored encrypted against your organization and the charge runs on your account. OtterFront is never in the path your money takes.

The CRM

Accounts and contacts, linked to each other, with a timeline of notes and calls on every record. Import a spreadsheet of either and duplicates are skipped rather than doubled.

Pipelines you define

Add a pipeline, name its stages and reorder them. Deals move on a board you drag, and a closed deal records why it closed. Nothing about your sales process is compiled into the product.

Pipelines only some people see

Mark a pipeline restricted and it is invisible to everyone without a grant, including in totals. Useful when one board holds numbers the whole team should not read.

Tasks with the record they belong to

Assign a task to a teammate against a contact, an account or a deal. My Tasks groups by when they are due and marks the overdue ones.

Capture forms you can embed

Build a form, drop it on any website, and submissions arrive as leads on the pipeline you chose. Rate limited and honeypotted, so a bot learns nothing from trying.

A lead funnel that converts

Leads move from subscriber to marketing qualified to sales qualified on their own board, and a converted lead becomes a contact, an account and a deal in one step.

Support tickets

Tickets numbered per organization, linked to the contact, the account and the deal, with a threaded conversation and internal notes that the customer never sees.

A dashboard

Open deal value by stage, what closed won and lost, and what is overdue, across the pipelines you are allowed to see.

Your team, with roles

Invite teammates by link and give each of them owner, admin, member or viewer. Every record in the product belongs to one organization and is only ever readable inside it.