Question 1

What does Tallyr consider when supporting dynamic pricing?

Accepted Answer

Tallyr reads pace, seasonality, and your floor rules to help place a rate decision in operating context. It works above the existing PMS and channel-manager stack rather than asking you to migrate platforms. The recommendation is context for the operator; the final pricing decision remains with your team.

Question 2

Does Tallyr respect minimum stays, booking caps, permits, and operator rules?

Accepted Answer

Yes. Tallyr is designed to operate inside market guardrails such as minimum stays, booking caps, permit requirements, and other constraints your team sets. Demand signals do not override a permit suspension, an operator-set floor, or a rule that makes a booking unsuitable.

Question 3

Which guest messaging channels does Tallyr cover?

Accepted Answer

Tallyr is designed to work across Airbnb, VRBO, SMS, WhatsApp, and email. Property and thread context carries across the operating workflow so a team can understand the conversation, its history, and the next action without treating every channel as an isolated inbox.

Question 4

Does Tallyr replace Hostaway, Guesty, or OwnerRez?

Accepted Answer

No. Tallyr works above systems such as Hostaway, Guesty, and OwnerRez. The goal is to connect the thinking and handoffs around your existing PMS and channel-manager stack, not to promise a platform migration or replace the systems that hold your operational truth.

Question 5

When does Tallyr draft a reply instead of sending one automatically?

Accepted Answer

Draft and review is the safe default for consequential or uncertain messages. Routine, fact-supported replies may be automated only within the rules you configure. When a request is ambiguous, sensitive, or outside those rules, Tallyr can escalate it for an operator to review rather than guessing.

Question 6

Can an operator pause automation or take over a conversation?

Accepted Answer

Yes. Your team remains the final decision-maker. Operators can edit a draft, pause or resume automation, set escalation and quiet-hour boundaries, and take over a thread when a human needs to speak. A thread takeover keeps Tallyr from speaking over the live conversation until the operator is ready to resume the configured workflow.

Question 7

What property and thread data does Tallyr use?

Accepted Answer

Connected property and thread context is used for routing, conversation history, drafts, and next actions. Keep sensitive credentials, full payment-card numbers, government IDs, unnecessary health or financial details, and unrelated personal data out of messages. Tallyr is an operating layer, not a reason to put more sensitive information into a guest thread.

Question 8

How does Tallyr handle retention and access to connected message data?

Accepted Answer

The current product does not promise a fixed retention or automatic deletion schedule. Operators should own and document the retention and access policy for their business and connected channels, including who can review or delete records and when. Use the process appropriate to your properties, jurisdictions, channel rules, and business agreements.

Question 9

What is the current Tallyr Maintenance Triage Pilot?

Accepted Answer

The founding Maintenance Triage Pilot is a $2,500 upfront, 14-day engagement available to the first five operators. It starts with maintenance triage so both sides can confirm the workflow boundaries, the handoffs, and the right starting scope before a broader product conversation.

Question 10

How long does broader Tallyr onboarding take?

Accepted Answer

The 14-day duration is specific to the founding Maintenance Triage Pilot, not a universal implementation promise. Broader onboarding depends on the properties, connected workflows, operator rules, and team boundaries confirmed in the pilot conversation. Tallyr does not promise one implementation duration for every portfolio.

Question 11

How much does Tallyr cost for a 100+ unit operator?

Accepted Answer

Operator 100 is $499/month for 100–199 units. Operator 200 is $899/month for 200–499 units. Portfolio 500+ is custom. Annual billing saves two months. Prices are in USD and exclude applicable taxes; final scope and onboarding are confirmed in the pilot conversation. See the full plan comparison at /pricing.

Question 12

Which Tallyr plan should a serious 100+ unit operator start with?

Accepted Answer

Operator 100 is the starting point for 100–199 units, while Operator 200 is the recommended path for teams coordinating 200–499 units. Portfolios of 500+ units need a custom scope. The pilot conversation is where Tallyr confirms fit, starting scope, and the onboarding path for your operation.

The questions that come up before you put AI above the stack.

Clear boundaries, by topic.

Dynamic pricing coverage

Multi-channel messaging

AI autonomy and overrides

Data and access handling

Rollout timeline

Commercial pricing

Bring the real workflow to the conversation.