Customer Support and Billing Automation for Storage Unit Facilities: Every Unit on Its Own Monthly Clock
Why a storage facility runs two genuinely separate operational tracks
A storage facility’s day-to-day support questions — is a unit available, what are the gate hours, how do I get my access code reset — have nothing to do with billing, and most tenants only reach out about one or the other, rarely both at once. But the billing side has its own real complexity: potentially hundreds of units, each with its own monthly due date and its own payment status, none of which should depend on someone manually checking a spreadsheet to know who is current and who is overdue. Treating both as one undifferentiated "customer contact" problem misses that they need genuinely different automation.
How the underlying problem shows up before you fix it
A tenant asking a simple access-hours question waits on the same informal channel as a genuine billing dispute, with no routing or priority difference.
Nobody has a single, reliable view of which of the facility’s many units are current on rent and which are overdue, without checking a spreadsheet by hand.
A rent reminder either does not go out consistently, or goes out to every tenant regardless of whether they already paid.
Confirming a payment landed and updating that unit’s status is a manual step someone has to remember to do for every single payment.
A tenant conversation from last month has no record attached when they message again this month, so context has to be rebuilt from scratch.
Why this keeps happening without two purpose-built systems
A single generic tool rarely handles both a real-time support inbox and month-over-month recurring billing well — support tools are not built for tracking dozens of independent billing cycles, and billing tools are not built for routing an inbound WhatsApp question. Without a system purpose-built for each side, a facility either under-invests in one (support goes informal and untracked, or billing stays a manual spreadsheet exercise) or spends real staff time bridging the two by hand every month.
How Centriu Link and Gauge cover the two tracks separately
Every inbound tenant message — WhatsApp, Instagram Direct, Messenger, or the facility’s web widget, Link’s confirmed real channels — lands in one queue with round-robin routing and an SLA, with full conversation history attached to each contact so a returning tenant’s context is never rebuilt from scratch. On the billing side, Gauge tracks each unit’s recurring monthly charge separately, sends an automatic email reminder ahead of the due date, and generates a boleto or Pix charge through Asaas. Once a tenant actually pays, a webhook from Asaas confirms it and Gauge automatically marks that unit’s charge as settled — no one has to manually reconcile which units paid this month.
What is actually built today
One shared queue for every inbound tenant conversation across WhatsApp, Instagram Direct, Messenger and the web widget.
Round-robin routing and an SLA on every conversation, with full history attached per contact.
Automatic email reminders ahead of each unit’s monthly due date.
Boleto and Pix charge generation through Asaas, tied to each unit’s own billing cycle.
Automatic write-off by webhook the moment a payment is confirmed — no manual reconciliation step.
A facility with 80 rented units at month-end (illustrative scenario, not a real client)
On the first of the month, Gauge automatically sends an email reminder to every tenant whose unit is due, without anyone manually checking which of the 80 units need one.
Mid-month, a tenant messages the facility’s WhatsApp asking about extended access hours for the weekend — a routine support question that lands in Link’s shared queue, gets routed to whoever is available, and is answered with no billing context needed at all.
A different tenant pays their overdue balance via the Pix charge sent earlier that week. Asaas’s webhook confirms the payment, and Gauge automatically marks that unit’s charge settled — nobody on staff has to cross-reference a bank statement to know that unit is now current.
What changes operationally
The structural change is two separate, purpose-built tracks — a routed support queue for tenant questions, and per-unit automatic billing with automatic payment confirmation — instead of one undifferentiated process trying to cover both. What that is worth in staff time saved or reduced late payments depends heavily on a facility’s unit count and current process — Centriu does not attach a specific figure that would generalize.
When this is not the right fit
A very small facility with only a handful of units, easily tracked by one person from memory, may see less specific value from separating support routing and automated per-unit billing.
One undifferentiated process vs. two purpose-built tracks
Handling tenant support and per-unit billing through one informal process means neither gets the automation it actually needs — support goes untracked, or billing stays a manual spreadsheet exercise. Centriu Link’s routed support queue and Centriu Gauge’s automatic per-unit billing and payment confirmation, used together, give each track the purpose-built automation it needs without forcing one into the other’s shape.
Related systems
Main system: Centriu Link. Complementary when relevant: Centriu Gauge.
What it does NOT do
- Does not manage physical unit assignment, gate access codes, or lock status — this is support conversation and billing, not a facility access-control system.
- Does not answer every tenant message with AI indefinitely — Link’s AI assistant responds up to the plan’s limit, then a human takes over.
- Does not guarantee a tenant will pay on time — it automates the reminder, charge and confirmation steps; the payment decision is still the tenant’s.
- Does not merge conversation or billing data across different facilities using Link and Gauge — each account only sees its own.
Security and governance
Each storage facility using Centriu Link and Gauge only sees its own conversations and billing data — nothing is shared across accounts. Tenant personal and financial data follows Brazil’s LGPD (Law No. 13,709/2018). Full detail on access control and audit trails lives at /governanca and /iso.
Pricing and contracting
Available by monthly subscription, with tiered plans. Values and terms come from the official pricing table at /precos (Centriu's central source — never restated here).
Frequently asked questions
Which channels does the shared support queue cover?
WhatsApp (via Baileys), Instagram Direct, Messenger, and the facility’s own web widget — Centriu Link’s confirmed real channels.
How does a unit’s monthly rent reminder go out?
Automatically by email ahead of the unit’s own due date, tracked per unit rather than as one facility-wide cycle.
What payment methods does the billing side support?
Boleto and Pix, generated through Asaas.
Does someone have to manually confirm a payment landed?
No — a webhook from Asaas confirms payment and Gauge automatically writes off that unit’s charge.
Does the AI assistant handle every tenant conversation by itself?
No — it responds up to the plan’s limit, then hands off to a human with the full conversation history attached.
What do Centriu Link and Gauge cost?
Link is sold by subscription with a published starting price; Gauge is offered by custom proposal — exact current terms are on the central pricing page or arranged directly with the team.
See how Centriu Link and Gauge handle storage-facility support and billing
Reach our commercial team directly, or leave your details below — we'll follow up with guidance for your case.