Frequently asked questions

zimrly is the operating system for your property: reservations, rates, availability, invoicing, official reporting and guest communication in one place instead of six logins.

There are two ways to run it. Either zimrly is your PMS, and the third-party system underneath goes away. Or you keep your booking system and zimrly reads from it. Both run in production, and you can switch later.

Possibly none at all: zimrly can be your PMS.

If you keep your own system, 3rpms and Smoobu run in daily operation at real properties. Built and in the pilot phase: apaleo, Cloudbeds, Beds24, Sirvoy, Hostaway and Guesty. In development: ibelsa and Mews. protel and others we connect on request.

€99 net per month for up to 10 rooms or bookable units, then €8 net per additional unit. A property with 14 rooms pays €131. Paid annually it is 20 percent less.

AI text and phone run separately on actual usage, and you set the monthly limit yourself. No setup fee, 30 days to try it without a credit card.

Automatically, line by line: accommodation at 7 %, breakfast and other services at 19 %, tourist tax on its own row. The invoice can go out as ZUGFeRD and XRechnung.

For OTA bookings only the guest's gross price lands on the invoice. The commission from Airbnb or Booking is a separate service billed to you, and it has no place on the guest's invoice.

Yes. zimrly calculates tourist tax (Kurtaxe / Fremdenverkehrsbeitrag) from your municipality's bylaws, including exemptions for business travellers or children.

Rates differ by region across Germany, Austria and Switzerland. You set this up once per property, and after that the amount is itemised correctly on every guest invoice.

Through the official WhatsApp Business API via 360dialog. zimrly sends booking confirmations, check-in reminders and arrival details automatically.

When a guest replies, the message lands in one central inbox. The AI assistant drafts an answer or handles simple enquiries on its own. You decide what goes out: approve each message, or let it send automatically.

All data sits on servers inside the EU: Supabase in Frankfurt, Brevo in France and Germany, Mistral in Paris.

Access tokens for your third-party systems are stored encrypted with AES-256-GCM. Every subprocessor is bound by contract, and the full list is in the privacy policy.

Yes, and you get it without email ping-pong. In the customer portal you read the DPA under Art. 28 GDPR, download it as a PDF and accept it digitally.

The acceptance is logged in an audit-proof way, with date, person and version. Before zimrly processes guest data in production, the current version has to be accepted.

No minimum term. On monthly billing the contract ends at the end of the month; on annual billing, at the end of the term.

You cancel from the dashboard, with no phone call and no letter. No setup fee, no hidden costs.

A wizard walks you through your master data and switches on what you need first. You do not have to connect a booking system for that.

If you want to keep yours, you connect it in the same flow, usually with an API token from its back end. Most properties are through in under an hour, with no IT department.

Two-factor authentication via TOTP app, with recovery codes for the day your phone is gone.

Roles separate owner, admin, manager and viewer cleanly, so each one only reaches what it needs. Provider credentials are stored encrypted, and security-relevant actions land in the audit log.

Owner-operated hotels, guesthouses, vacation rentals and contractor accommodation across the DACH region, typically between 8 and 100 units.

Properties that face the same paperwork as a chain: § 14 invoices, tourist tax, guest registration, DATEV. Just without a chain's staff or a chain's budget.