Fede asked for deep research on "apps like grok bot and Viktor": how they work, and what we can take for Clara. Both turn out to be general AI coworkers that live in a team's chat. The AI leasing assistants are covered too, so we can see where Clara stands.
Nov 1, 2026 · Proposed — pending Fede's review · research only, nothing built · vendor claims are marked "vendor"; secondhand reports are marked "2nd-hand" · related: teammate memory, staff tour moves
The leasing bots talk to renters. The coworker agents talk to the team. Every leasing assistant we looked at answers prospects and books tours, much like Clara. Almost none let the leasing staff simply message the AI and hand it work. Viktor and OpenClaw are built around exactly that: they sit in the team's chat, read every thread they are in, act when someone asks, write down how the team works, and check in on a schedule. That is the half of Clara we are building now.
| Fede said | Best match | Confidence | Why | Other candidates |
|---|---|---|---|---|
| "Viktor" | Viktor (viktor.com), "the AI employee" that lives in Slack and Microsoft Teams. Raised $75M from Accel in May 2026. | High (~90%) | Exact name; it is the best-known "AI coworker" of 2026 and has its own property-management page. | No leasing product called Victor or Vektor exists. Similar-sounding leasing names (Lea, Kelsey) are in the table below. |
| "grok bot" | Clawdbot, renamed Moltbot and then OpenClaw (Jan 27 and 30, 2026). Free, open-source personal AI agent by Peter Steinberger. | Medium-high (~75%) | "Clawd-bot" sounds like "grok bot", and Viktor sells itself against it: its CEO's post on X compares the two head on ("We said Viktor is OpenClaw for Slack. It's not."). | BetterBot, a leasing chatbot (~15%, in the table). xAI's Grok (~10%): it has no leasing product. |
The brief guessed BetterBot for "grok bot". The pairing with Viktor points to OpenClaw instead, so this page goes deeper on the two coworker agents and keeps BetterBot in the market table.
| Viktor | OpenClaw (was Clawdbot) | Clara today | |
|---|---|---|---|
| Where it lives | Slack, Teams, Discord, a web app. One shared Viktor per company. | Your own computer or server; WhatsApp, iMessage, Slack, Teams, Telegram and 20+ more. One per person. | Text, email and phone, on the customer's line and mailbox. |
| How the team talks to it | Name it in a channel, or message it privately. It replies in the thread where the work came up. | Direct messages; in group chats it answers only when named. | Staff text or email Clara one to one. |
| Group threads | Works in the channel; keeps each channel's context separate. | Reads every group message as context, replies only when named. Strangers must be approved. | Not yet on reply-all email threads with several staff. |
| Memory | Company-wide memory built from the channels it joins; admins can wipe it. | Plain text files: who you are and how you like things, lasting facts, a daily log. "Only remembers what gets saved." | Five fixed settings per person; nothing free-form (proposed Nov 1). |
| Learns the team's ways | Watches workflows and writes them up as "skills"; suggests automations, the team decides. | Writes its own skills, announces each one, keeps the old version for undo. | No. |
| Acts on its own | Scheduled jobs set up from chat (Monday report, "alert only when a human is needed"). | A check every 30 minutes; says nothing when there is nothing to report. | Reminders and follow-up texts to renters; no check-ins with staff. |
| Approvals | Admin picks which actions need a yes; sends and payments wait for a yes in the thread. | Code-level limits; no per-action approval found. | Acts on its own (our rule: no approval buttons). |
| Price | $100/month for 40,000 credits shared by the team (about 80 to 400 tasks); free $100 to start. | Free; you pay the AI model's bill. | — |
All claims are from the vendors' own pages unless marked. Most publish nothing on how staff talk to the AI, on what they write into the property software, or on how they reschedule.
| Product | Channels | Property software | What staff get | Learns team habits? | Price |
|---|---|---|---|---|---|
| EliseAI | Text, email, chat, voice (7 languages) | Major systems (list not readable) | "Agent" phone app: only the work that needs you, one schedule across properties (Mar 2026). "Apollo": ask in plain words, it does anything the app can, within your permissions (Sep 2026). | Learns each team's settings; no habit memory stated | ~$3–6/unit/mo, ~$25K minimum (2nd-hand) |
| BetterBot | Chat, email, text, voice in one thread | Not named | One leasing dashboard; "agents stay in charge" | No | Quote |
| Zuma (Kelsey) | Leasing chat, voice receptionist, collections | RealPage, Yardi, Entrata, Knock | Tours land on the onsite team's calendar; human experts behind the AI | Not stated | Quote, free pilot |
| Funnel | Email, phone, text, chat | Yardi, RealPage, Entrata | Built for centralized teams; follows the team's procedures | Follows set procedures | Option to pay per resolved conversation |
| Knock / RealPage AI Leasing Agent | Email, text, voice, chat | RealPage | On hand-off, a summary of the conversation appears in the CRM | No | Quote |
| LetHub | Email, phone, site chat | Not Yardi (by its own blog) | Two-way calendar sync; round-robin showing assignment (beta) | No | Not public |
| Respage (ResMate) | Chat (others not listed) | AppFolio, Entrata, RealPage, Knock | "Experts in the loop"; live in 5 business days | No | Bundle ~$279/property (2nd-hand) |
| Hyly (Hayley) | Chat, email; voice "coming soon" | Not stated | Alerts that re-engage quiet leads; hands off "with complete context" | No | $199–299/property/mo |
| Lea Pro (Apartment List) | Phone, email, text, chat | Not stated | Multi-touch follow-up | No | Not public |
| Tour24 | App for self-guided tours | Not stated | Flags hot leads vs casual visitors | No | Quote |
| AppFolio Realm-X Leasing Performer (no "Lisa" in 2026 sources) | Voice, text, email | AppFolio: creates guest cards, adds recordings, transcripts, tags | Staff can watch calls live; offers a similar unit or a sister property when one is gone | Not stated | Not public |
| Yardi Chat IQ / Virtuoso | Chat, email, text, voice | Yardi | Flags unanswered questions to the team; changes its planned follow-up if an agent already took the next step (event recap; verify) | Not stated | Bundle, quote |
| Entrata ELI+ (absorbed Colleen AI, 2024) | Same channel the lead used; 30+ languages | Entrata: logs every interaction | Oct 2026: one shared context across calls and messages; operator controls hand-offs | Not stated | Suite, quote |
| Rentgrata | Not an AI: current residents answer prospects' questions. Out of scope. | ||||
| Clara | Text, email, phone | AppFolio: guest cards and notes | Staff text or email her; tour alerts; after-tour notes ask | Not yet (proposed) | — |
Ranked by how directly each fills a gap in Clara as a coworker.
| # | Idea | Seen in | Gap it fills | What it would look like for Clara |
|---|---|---|---|---|
| 1 | When corrected, write one short note and say so. Undo is one message. | OpenClaw skill writing; Viktor "skills" | Teammate memory | Kat says "I'll show A.N. right after B, same address." Clara replies "Got it, I'll stack tours at the same address for you" and remembers it. |
| 2 | In a group thread, read everything, answer only when named or when it's her item. | OpenClaw group chats | Reply-all threads | On a reply-all email with three staff, Clara takes in the whole thread and replies only to what is hers. |
| 3 | Do anything in plain words, within that person's permissions. | EliseAI Apollo | Staff by email; tour move and reassign | "Move Maria's 3 PM to Thursday and give it to Ryan" by text or email, no app. |
| 4 | Standing orders given in chat. "Every evening, send me tomorrow's tours." | Viktor scheduled jobs | Replacing the virtual assistant | A staff member sets a recurring job by asking; Clara confirms and runs it. |
| 5 | Check in on a schedule, stay silent when nothing needs a person. | OpenClaw heartbeat; Viktor alerts | Cover requests | Clara notices an agent is out tomorrow with three tours booked and asks the team who covers. |
| 6 | Don't send a follow-up a person already sent. | Yardi Chat IQ | "Did a person already reply" (open row 14) | Before each follow-up, Clara looks for a staff reply since her last touch. |
| 7 | Shared team memory, plus a private lane per person. | Viktor | Teammate memory | Team facts ("same-address tours stack") live with the company; personal likes ("text me, don't email") stay with the person. |
| 8 | Introduce yourself and ask how each person likes to work. | Viktor onboarding | Teammate memory; new teams | The welcome text asks one question: "Anything I should know about how you run tours?" |
| 9 | Hand-off summary where staff already look. | Knock / RealPage | Staff notices | Every hand-off note opens with three lines: who, what they want, what Clara already did. |
| 10 | Share showings fairly, and offer the sister home when one is gone. | LetHub round-robin; AppFolio Leasing Performer | Tour reassign; booking the tour | Rotate new tours across the showing list; if the home is leased, offer the closest match instead of a dead end. |
| Complaint | Where | How Clara avoids it |
|---|---|---|
| Bot sent several follow-ups before staff arrived in the morning | EliseAI, BetterBot (Reddit, 2nd-hand) | Stop rules; check for a staff reply first (idea 6) |
| More tours, worse tours: tour bookings up ~5%, closing rate down ~10% | AppFolio's earlier leasing AI (2nd-hand) | Judge Clara on tours that lease, not tours booked |
| Wrong answers that staff had to fix | BetterBot | Answer from the property's facts only; ask when missing |
| "Glosses over or assumes things that are quite important" | Viktor (G2 via a competitor) | When a staff order is unclear, ask once, briefly |
| Five-paragraph answer to a quick question | Viktor | Staff replies stay one or two lines |
| Context doesn't carry between channels | Viktor | One person, one history, across text, email and phone |
| Surprise bills: a 5-person team out of credits in 36 hours; agents burning $200–500 a day on check-ins | Viktor (2nd-hand); OpenClaw (2nd-hand) | Check-ins are cheap lookups first; the model runs only when something changed |
| Add-ons that steal data: 341 of 2,857 shared skills were malware; a one-click takeover flaw | OpenClaw (security researchers) | Teammate notes are plain text, never code, never from outside |
| A personal Gmail connected as a team tool, exposed to everyone | Viktor (case study) | Personal and shared mailboxes stay separate |
| Self-tour app rated 2.1–2.3 stars: booking never went through, lockbox failed | Tour24 (app stores) | Prove every booking end to end; a lockbox code is checked before it is sent |
| Every message to tenants waits for a person's yes, permanently | Viktor's own property-management advice | Deliberately different: Clara acts and is fixed in the engine |
Recommendation: fold ideas 1, 2 and 6 into the coworker work already planned. Idea 1 is the teammate-memory proposal with one added line ("say what you learned"). Idea 2 is the reply-all gap. Idea 6 is open row 14. The rest wait until those three are live and proven at Willows. Fede: yes / hold.
Research done Nov 1, 2026 from public pages only; no demos, no logins. Very few independent reviews exist for any leasing product, and no first-hand Reddit threads were found; complaints marked 2nd-hand come from comparison blogs quoting Reddit. Viktor's G2 and Product Hunt ratings (4.9) rest on 17 to 51 reviews.