- How is TailRoster actually different from Gingr?
+
- Gingr is a database with a booking form on top. TailRoster is the room itself — phones answered, vaccines verified, deposits taken, holiday surcharges priced correctly, all before you open the laptop. Same data model your staff already knows. A front desk that doesn't sleep. If you can't see the difference inside one shift, we'll refund the month.
- What about migrating my customer DB, pets, reservation history?
+
- One click. You paste your Gingr export, we map customers, pets, vaccines with their original photos, package balances, deposits, gift cards, recurring appointments, and behavior notes. A reconciliation report flags anything ambiguous so you fix it before go-live. If we can't migrate you in a day, we'll explain why before you commit.
- Can I run TailRoster alongside Gingr while we transition?
+
- Yes. Most operators dual-run for one to two weeks — bookings flow into TailRoster, Gingr stays read-only for historical lookups. Stay tier includes 14 free days of parallel running, Heel includes 30, Pack includes 60. Cut the cord when your front desk stops opening the Gingr tab. Usually that's Friday of week one.
- Will my older staff actually use it?
+
- Yes, and faster than your younger staff did on Gingr. The check-in screen is one tap. The drag-drop calendar looks like a paper roster because that's what they're used to. Median time from new-hire login to first solo check-in is 38 minutes. We have kennel managers in their sixties running entire weekends without opening the help docs.
- Does the AI front-desk creep customers out?
+
- No, because we tell them. The opening line is "Hi, I'm TailRoster, the front desk AI for [your facility] — happy to help." Customers consistently rate it higher than voicemail tag with a human who's elbows-deep in a Bichon. The AI never pretends. It never invents policy. It hands off to a person inside thirty seconds when something feels off.
- What's the SLA? What if TailRoster is down?
+
- We're early in our operating record, so we're not publishing an uptime number we can't yet stand behind. What we will commit to today: incidents are posted to our changelog within the hour, and a support contact reaches an engineer on the team — not a tier-one queue. Once we have a meaningful operating history, we'll publish a measured uptime target and the credit terms that go with it.
- Why no per-transaction fee? What's the catch?
+
- No catch. Gingr's per-transaction model exists because their pricing was set in 2014 and they can't undo it without breaking their P&L. We priced from a clean sheet in 2025: flat monthly, unlimited staff, unlimited AI. Payment processing fees go directly to Stripe, Square, or Clover — same rates you'd pay them anyway, no skim from us.
