Transparency
Known Issues
We list known limitations openly. The-Y CRM is in an early Alpha — things change. Unfixed security issues are deliberately not listed here (see note at the bottom).
As of: 2026-11-08 (version 1.1.60) · Phase: Alpha · The limitations per version are also listed in the Release Notes.
Legal & commercial
| Item | Impact | Status / workaround |
|---|---|---|
| Founder purchase | Public Founder purchase active: €10.00/month (total incl. any VAT), clean B2B checkout with company name, VAT ID and binding consent | ✅ Active (Alpha) · businesses only (B2B) |
| Founder scope | Defined (price, scope, reactivation, voluntary 14-day return right, hosting) — Terms §6 | ✅ Released in v1.1.1; license key sent by email right away |
| Terms · Privacy · DPA · In-app terms | Current versions: Terms of Use 1.6, Privacy 1.17, DPA 1.9 (1.10 applies from 2026-12-01), in-app terms 1.6 — each with an immutable snapshot + SHA-256 in the Legal Archive | ✅ As of 2026-11-08 |
| Accounting features | A tool for your own records up to the hand-over to your tax advisor — not tax advice; retention and returns remain your responsibility | Covered in the Terms of Use, section 4a (since 1.4) |
| Backup guarantee | Automatic backups run, but during the Alpha there is no formal recovery commitment | Also back up yourself via snapshot/CSV; binding backup policy from Beta (DPA Annex 3) |
Channels: WhatsApp, Facebook & Instagram
| Item | Impact | Status / workaround |
|---|---|---|
| “Number not verified” notice | The dashboard showed “WhatsApp: Number not verified” even for numbers that are connected and working normally | ✅ Fixed in 1.1.58: the notice only shows when the number is not connected |
| Several Facebook Pages in one account | Older Messenger/Instagram conversations only get their Page with the customer's next message | Known (1.1.26); new conversations are assigned correctly right away |
| Existing Facebook/Instagram connections | The linked Instagram account only appears as a channel of its own after connecting again | Run “Connect Facebook & Instagram” once more — nothing is created twice (1.1.28) |
| Fixing undelivered messages | Only admins see “Connect channel →” and “Send again” | Team members without admin rights see “Please let an admin know” (1.1.29) |
| WhatsApp verification “By call” through a phone system with a greeting | The greeting talks over the code being read out, and Meta hangs up | Route the number straight to a phone for the call; with the phone system in the CRM via “Put the code call straight through to me (10 min)” (1.1.32) — needs your own extension; without number detection all incoming calls go to you during these 10 minutes (guide) |
| Blocking WhatsApp contacts | Meta only allows blocking if the customer wrote in the last 24 hours | Meta rule; only admins can block (1.1.25) |
| Messenger greeting text | Meta has retired the old greeting text on the welcome screen | Use “Get started” with an automatic reply instead (Meta hub) |
| Page name, images, category, address (Facebook) · bio/website (Instagram) | Can't be changed through Meta's API | Guide + direct link in the Meta hub; Meta only shows Instagram conversation starters in the app |
| Display name for numbers with the WhatsApp Business app | Re-registering after approval is done by the app, not the CRM | Known (1.1.25); only Meta support changes Official Business Accounts (green tick) |
| Reset or delete account | Doesn't yet automatically revoke WhatsApp access at Meta | Delete the WhatsApp channel first — that ends the access (1.1.22) |
| Posts: reach | Meta only shows reach in Business Suite | Deliberately no extra statistics permission (1.1.24); likes, comments and shares are in the CRM |
| Comments | According to Meta, a private reply only once and within 7 days; no “Like” on Instagram comments; Instagram doesn't report deletions/edits by the author | Meta rules (1.1.24) |
| Fetching comments | The direct fetch covers comments from the last 7 days on the 10 most recent posts; Meta doesn't always include the name of the person commenting | Known (1.1.27); otherwise comments also arrive via Meta's notifications |
| Delete a contact permanently | If, after connecting the WhatsApp Business app, the history only arrives after the deletion, the person is created again from it | Known (1.1.20); delete again afterwards |
| One page, one number – one account | A Facebook Page, an Instagram account or a WhatsApp number can only be connected to one The-Y account. The connection status isn't shown in the channel view yet | Known (1.1.39); if a page or number is already connected to another account, write to us and we'll clarify who it belongs to |
| WhatsApp customers with a username | Meta only delivers verification-code templates to phone numbers. If a customer removes their username, the last known one stays visible | Meta rule / known (1.1.33) |
| Reactions | WhatsApp reactions to older messages and to campaign messages are not shown; you see a new reaction when you open the conversation again. Reactions from Messenger and Instagram are not shown yet | Known (1.1.40) |
| Files from Messenger and Instagram | If a file is very large (over 25 MB) or the link has already expired, the conversation only shows a notice | Known (1.1.40); open the file in Messenger or Instagram |
| Observing when Meta's AI agent runs a conversation | Conversations run by another responder (e.g. Meta's AI agent) only reach the CRM if you allow observing ("standby") for The-Y CRM in Meta Business Suite. Otherwise nothing from these conversations arrives | Technical limitation (1.1.44); the card "Conversation routing at Meta" shows a red warning and the steps (guide) |
| Who is running the conversation? | Meta does not continuously report who runs a conversation; the CRM derives it from Meta's notifications. The status shown can briefly be off | Known (1.1.44); it corrects itself with Meta's next notification or your next reply |
| Handover to you and first-response deadline | If a conversation you have been observing is handed over to you, no new first-response deadline (SLA) starts. The resolution deadline runs as usual | Known (1.1.44); the team is notified on handover and the conversation opens like a new request |
| Taking over or handing back a conversation | "Take over conversation" only works if The-Y CRM is the escalation partner at Meta; "Back to Meta's AI agent" only if the AI agent is switched on for the number. Escalation and observing only appear in Meta Business Suite after you have accepted the terms for Meta Business Agents | Meta rule (1.1.44); this can only be set up in Meta Business Suite (4 steps) |
| Observed Messenger and Instagram messages | Images and attachments appear as placeholders. Whether you can take over a conversation depends on which application is set as the default for your Page at Meta | Known (1.1.44); open the file in Messenger or Instagram |
| Marketing templates via Meta's Marketing Messages API: costs | The cost overview in the CRM estimates marketing messages based on Meta's list price. Meta's maximum price model (from 2027 depending on the region) is not included yet | Known (1.1.44); Meta's billing is what counts |
| Turning on the Marketing Messages API at Meta | Only someone with full control of your Meta business portfolio can click "Accept terms" at Meta. For the CRM, "added" (deadline 13 Apr 2027) means the day the number was connected in the CRM | Meta rule / known (1.1.44); otherwise send the instructions to the person who manages your Meta account (guide) |
| "Stop marketing messages" in WhatsApp | Only works for contacts the CRM finds by number or WhatsApp ID; no new contact is created. "Resume promotions" is not new consent | Intended (1.1.44); marketing still needs explicit consent |
Phone
| Item | Impact | Status / workaround |
|---|---|---|
| Answered calls without the CRM phone | If a call is forwarded and only the mobile's voicemail picks up, it counts as “answered” – an open conversation is created. Conversations from calls without the CRM phone aren't assigned to anyone | Known (1.1.58); assign or close the conversation |
| Call flow as a diagram | In the call flow editor one line ran out of the picture, the line from the phone number to the queue was missing, and the “Otherwise” node was labelled twice | ✅ Fixed in 1.1.59: the lines end at the nodes; “Otherwise (default target)” shows “Calls without a matching number” below it |
| Phone numbers | Phone numbers are not yet in the same format everywhere | Known (1.1.58) |
| Forwarding to your mobile after the greeting | If a group plays a greeting while it rings and the call then goes to an external number (e.g. a mobile), the system answers right away – the caller pays from the greeting on (as with a menu). Groups without a greeting and groups that only forward internally stay free for the caller until someone answers | By design (1.1.54); fixes “subscriber not available” |
| “Always play the greeting” | When ticked, the system answers the call right away, so the caller pays from the greeting on. If nobody can answer, the caller still waits for the ring time before the call moves on to “If nobody is free” | By design (1.1.54); unticked by default |
| “Don’t sign in the phone in this browser” | Applies only to the browser where you tick it; a private window forgets it when closed | Known (1.1.54) |
| Live tests 1.1.53 | Not yet confirmed with real calls: the phone assistant and the “Waiting line” phone template on a real number, “My mobile rings too” added by the person themselves, a complete call list after the phone system restarts | Live tests are running (1.1.53); results and deviations will be listed here |
| “My phone” and “Setup” | Settings → Phone takes admins to “My phone” too. The call-route view (call flow) is unchanged on mobile. “My recent calls” does not show answered calls whose conversation belongs to someone else | Known (1.1.53); click “Setup” at the top of telephony, all calls are under “Calls” |
| Mobile number for “Mobile rings too” | Only the person themselves adds their number; admins see it shortened (“+43 … 67”) and can only remove it. After someone leaves, the number stays until an admin removes it. When an extension is assigned to someone else, the previous person's number is removed (you are asked first). Account backups contain the full number | By design (1.1.53); remove under Phone → Extensions (guide) |
| Phone templates “Reception” and “Medical practice” | The “Record calls” switch only exists for “Reception”. The emergency note of the practice template follows the phone number or the account's country and is fixed when applying; Switzerland gets 112 | Known (1.1.53); adjust the script yourself if needed and record it again |
| “Your account's recordings” | Also counts recordings that aren't used in any call route | Known (1.1.53) |
| Call list after a restart | Calls rebuilt after a restart or “recovered” from a recording have fewer details (e.g. no voicemail note, “in call since” estimated). Calls that run entirely during an outage and have no recording are still missing | Known (1.1.53); further matching planned |
| Live tests 1.1.52 | Not yet confirmed with real calls: position and callback in queues, mobile rings too (accept with 1), templates on a real number | Live tests are running (1.1.52); results and deviations will be listed here |
| Queue: position, waiting time, callback | Without your own recordings the position is announced with the English standard voice; waiting time and the callback offer need your own recordings. The waiting time is an average for everyone waiting and only comes once at least 3 calls were answered in the last hour (after a restart of the phone system none for up to 1 hour). Position only up to 10. With a callback the place is given up; there is no push notification to the mobile for it yet | Known (1.1.52); record the announcements yourself (guide) |
| Mobile rings too | Only over a line of your own; the mobile counts as another simultaneous call. In queues it rings again with every attempt. In a group call with keys or recording the mobile only rings if the person is signed in in the browser or on the desk phone. The mobile usually shows the company number. If the person is on a call on the mobile, the extension doesn’t count as busy | Known (1.1.52) |
| Phone templates and base settings per brand | No logo announcement with “greeting, then hold music” and before a queue’s greeting on entry. Queues created from templates don’t automatically get extensions you add later. “Turkish” from the brand kit has no effect in the phone system. “Restore previous target” is a button only right after applying | Known (1.1.52); later switch back under Telephony → Numbers or in the call flow |
| Telephony setup help | “Test call” is only detected when the phone system logs calls. “Worth checking” doesn’t check WhatsApp lines. “Undo” in the call flow covers the last change. Existing menus and queues keep “Hang up” as their destination | Known (1.1.52); the warning shows “Hang up”, change the destination if needed |
| Live tests 1.1.46 | Not yet confirmed with real calls: which audio format the browser picks for calls from the line (otherwise the phone system converts as before), the announcement above the limit for simultaneous calls, WhatsApp calls above the limit, and whether the notice before a recording is clearly audible | Live tests running (1.1.46); results and deviations will be listed here |
| Announcements without your own recording | Since 1.1.51 there are no computer voices any more. Without your own recording callers hear, depending on the announcement, a standard English prompt (e.g. “All circuits are busy now”, spoken by Allison Smith, Asterisk Core Sounds, CC BY-SA 3.0), a short tone or a moment of silence. Older announcements with a computer voice keep playing | By design (1.1.51); Phone → Setup shows what is still missing under “Your account's recordings” and for each fixed announcement. Record announcements in the browser or upload a file |
| Notice before a recording | Without your own recording callers only hear a tone before the call is recorded. That is not sufficient notice | Record the notice yourself, in your callers' language; the app shows a clear warning (1.1.51) |
| Recording in the browser | Checked in Chromium browsers (Chrome, Edge); Safari and Firefox not yet. Recording is blocked during an active call (same microphone). The queue's waiting announcement has no recording block yet | Known (1.1.51); uploading a file always works |
| Announcements from before 1.1.51.1 | Announcements you already saved are not converted again and sound as before. Very quiet recordings are raised, and the noise with them | Known (1.1.51.1); record or upload them again for the better sound. The app warns about recordings that are too quiet |
| Ring group with keys (ringing during the greeting) | With keys or recording the system answers immediately, so the caller pays from the first second. Single-digit keys only. If all members are on “Do not disturb” or logged out, the call goes straight to the destination – with “Always play the greeting” (since 1.1.54) the caller first hears the greeting and waits for the ring time. Not yet confirmed with real calls | By design (1.1.51); live tests are running |
| Priority in queues and ring groups | A higher tier rings when nobody in the lower tier is free, not after a waiting time (“first Anna for 10 seconds, then everyone” is not possible yet) | Known (1.1.51) |
| Hold music | Holding during a call plays the account's default music, not that of the number or brand. Music under an announcement only uses the first file of the music. Without music of your own, callers hear the server's standard music | Known (1.1.51) |
| Emergency calls | Emergency calls only work via your own line; without a line an emergency call fails. Emergency numbers of other countries dialled with a country code (e.g. +49 110) count as a normal call. An existing extension with an emergency number must be changed the next time you save it | By design (1.1.50); register your location with your line provider |
| Re-activating a member | Deactivated members can no longer make calls, effective immediately. After re-activation a desk phone needs the new password | By design (1.1.50); “Connect device”. The softphone in the browser reconnects by itself |
| Self-hosted without a paid key: 2 simultaneous calls | Without a paid key an installation counts as Free. The third simultaneous call hears the “all lines busy” announcement (or voicemail or busy, depending on your setting). With a paid key there is no plan limit, only the server limit PBX_MAX_CONCURRENT (default 80) | By design (1.1.46); adjustable without a new update via PBX_CONCURRENT_FREE (-1 = no limit), see self-hosting |
| Devices after the phone system restart | For 1.1.46 the phone system is restarted once (in the cloud on 18 Oct 2026, self-hosted when you recreate the Asterisk container). Afterwards all devices have to register again. Browser softphones do this by themselves within seconds, desk phones and softphone apps only at their next registration interval, often after 1–60 minutes. Until then they cannot be reached | Known (1.1.46); restart the device or app, or register it again. The CRM restores “Do not disturb” by itself |
| Phone system changes (crm.the-y.at) | Greetings, menus, extensions and number destinations changed in the CRM since 25 September didn't reach the phone system | ✅ Fixed in 1.1.32: changes take effect within a few seconds; everything saved since 25 September is applied once with the update |
| Running the phone system yourself | After updating to 1.1.32 a one-time reload is needed | Steps under Set up telephony → Troubleshooting |
| Several phone numbers on one line | The phone system recognises the dialled number automatically with Zadarma; without number detection the destination of the topmost number (⭐) applies | Still to be confirmed with real Zadarma calls (1.1.32) |
| Greeting while it rings | Only with your own greetings (recorded in the browser or uploaded as a file) | 1.1.32; since 1.1.51 ring groups can also ring during the greeting |
| One call = one conversation | Duplicate call conversations from before the update stay and are not merged automatically. The WhatsApp or SMS callback after “1 for WhatsApp” deliberately has its own conversation | Since 1.1.41; both conversations link to each other with “Open linked conversation”. After the update, reload the app in your browser once (Ctrl+F5) so the softphone sends the call ID |
| Confirmation after “1 for WhatsApp” | Since 1.1.51 no computer voice reads out a default text any more. Without your own recording callers hear “Thank you. Goodbye.” (standard English) after pressing 1. Older confirmations with a computer voice keep playing | Record the confirmation yourself (in the browser or as a file); since 1.1.41 the call flow and the template show whether WhatsApp, SMS or nothing really goes out after key 1 (guide) |
| “Press 1 for WhatsApp” | The chosen WhatsApp template must be approved by Meta. At most one message per number goes out in 24 hours; numbers that opted out of WhatsApp get none | Abuse protection, by design (1.1.34) |
| Automatic holidays | Public holidays are only added automatically for Austria and Germany | Other countries: your own list under Settings → Opening hours & holidays (1.1.34) |
| Template “Trades – never miss a call” | The greeting texts are in German | Known (1.1.34); adjust the texts if needed |
| Voicemail instead of hanging up | Also applies to internal calls and transfers | By design (1.1.34); ring time and destination can be set per extension |
| Voicemail on the phone | On the phone, old messages are deleted after 30 days | They stay in the CRM (1.1.40) |
| Softphone in the browser | Calling in the browser only works with an extension assigned to you | By design (1.1.39); assign one under Phone → Extensions |
| No call waiting | If you are already on the phone, another caller gets “busy” or your fallback destination. While you are calling in the browser, your desk phone doesn't ring either | By design (1.1.40) |
| Deleting building blocks | Extensions, menus, groups, queues, announcements and opening hours can still be deleted after confirming, even while they are in use; references are not moved automatically | Known (1.1.40); change references first |
| Desk phones and apps without a browser | Their calls are matched by number as before (no call ID) | Known (1.1.40) |
| Line status | “Not connected” does not distinguish between a wrong password and “provider not responding” | Known (1.1.40); check the credentials, then “Check now” |
WhatsApp calls (since 1.1.45)
| Item | Impact | Status / workaround |
|---|---|---|
| Live test with real calls via Meta | Real WhatsApp calls work end to end: the system answers, menu, ring group, answering in the softphone. Not yet confirmed: key presses in the menu (DTMF) on WhatsApp calls | Live test running (1.1.45.1); results and deviations will be listed here |
| Number with the WhatsApp Business app | WhatsApp calls only work with numbers that do not also run in the WhatsApp Business app. Otherwise they keep ringing only on the phone | Meta rule (1.1.45); for calls in the CRM use a number only for the CRM (guide) |
| Messaging limit and payment method | Meta requires a messaging limit of at least 2,000 (a new Meta business portfolio starts at 250; since 7 Oct 2025 all its numbers share this limit) and a payment method on the WhatsApp account – also for incoming calls. The CRM cannot read whether a payment method is set up at Meta | Meta rule (1.1.45); the CRM tells you as soon as Meta rejects a call because of it |
| No forwarding into the phone network | WhatsApp calls cannot be forwarded into the telephone or mobile network – not via a menu key, overflow or fallback either. The phone system then uses the fallback | Meta rule (1.1.45); answer on the go with the softphone in the app on your phone (guide) |
| Recording | The phone system played no notice of its own before a recording – also on phone calls | ✅ Fixed in 1.1.46 (guide). Since 1.1.51 you record the notice “This call is being recorded” yourself; without your own recording the caller only hears a tone, and the app warns you |
| Further Meta limits | Customers can only call from WhatsApp on a phone, not from WhatsApp Web. It can take up to 7 days until everyone sees the call button. If too many calls go unanswered, Meta hides the call button | Meta rule (1.1.45); put a voicemail box at the end of every path, leave call hours at Meta off |
| Call back via WhatsApp | Only with the customer’s permission. Meta allows at most 1 request per 24 hours and 2 per 7 days; after 4 unanswered calls in a row WhatsApp revokes the permission. You need your own extension. On the first call the customer may only see the number | Meta rule (1.1.45); the CRM warns from the 2nd unanswered call |
| Cost overview | The CRM estimates outgoing WhatsApp calls at Meta’s list price | Known (1.1.45); Meta’s billing is what counts |
| Self-hosted | WhatsApp calls need their own setup (public name with a valid certificate, port 5071 only for Meta, RTP 10000–20000). Without it the card shows “This installation is not set up for WhatsApp calls” | Since 1.1.45, see guide; when updating by hand, first the app, then the worker |
Video meetings & booking links (since 1.1.54)
| Item | Impact | Status / workaround |
|---|---|---|
| Camera and screen at the same time | While you shared your screen, the other person saw the screen instead of your camera | ✅ Fixed in 1.1.58: your camera appears small and round in the bottom right of the shared picture (“Also show my camera, small”, can be turned off) |
| Camera bubble while sharing | Only on a computer and in browsers that can record a canvas. If the video tab is in the background, the shared picture can stutter briefly. With the bubble, “sharp” keeps sending about 10 frames per second instead of about 1 (a bit more data) | Known (1.1.58); if it stutters, turn the bubble off |
| Screen sharing “sharp”: few frames per second | The shared screen arrives sharp, but with few frames per second (at most 10, often just one when the picture is still) – so text stays readable. With movement, e.g. scrolling or videos, it looks a bit choppy | By design for “Text and forms (sharp)” (1.1.54). Since 1.1.58 you can choose “Video and movement (smooth)” before sharing: up to 30 frames per second, a little less sharp |
| Screen sharing on phones and tablets | On phones and tablets you can usually only watch, not share – the browsers there don’t allow it | Known (1.1.54); use a computer to share |
| Weak connection | On very weak connections the picture gets blurrier or choppy first; sound has priority and should keep going | By design (1.1.54); the “i” in the picture shows how the connection is doing |
| Booking links: own time windows | At most 4 time windows per day. Time off, other appointments and public holidays still block slots. If a link has several hosts, its times apply to all of them | Known (1.1.54); without custom times your working hours apply |
| Booking links: display name | Reminders and emails about a rescheduled appointment still show the user’s name, not the link’s display name | Known (1.1.54) |
| Online booking: “From the next day” | Follows your account's time zone, not the guest's. If “earliest in X days” (only via the API) is larger than “how far in advance”, there are no free times | Known (1.1.58) |
| Menu item “Online booking” | Like the calendar, it can't be hidden under Settings → Sections | Known (1.1.58) |
Demo, sign-up & emails (since 1.1.56)
| Item | Impact | Status / workaround |
|---|---|---|
| Emails to customers without your own mailbox | Booking confirmations, appointment invitations and reminders to contacts, and the customer survey by email only go through your own mailbox. Without a mailbox they are not sent. There is no list of unsent emails in the CRM | By design (1.1.56); connect a mailbox under Settings → Channels – the places affected show the note “Connect mailbox” |
| Notifications via our system mailbox | Without your own mailbox, notification emails to your team only say that there is something new and link into the CRM – no names, message texts or figures. The report summary then also comes without figures | By design (1.1.56); with your own mailbox they include the content as before |
| Demo: the customer’s reply | In the sample conversation the customer replies a few seconds after you. If the tab is in the background or you have already left the conversation, the reply arrives as soon as you look back in. The “View only” sample company still starts on the overview | By design (1.1.56) |
| Sign-up without a company name | After “Reset account” the provisional name stays, but the note under Settings → Company no longer appears | Known (1.1.56); you can still change the name there at any time |
Sign-in with an email link (since 1.1.57)
| Item | Impact | Status / workaround |
|---|---|---|
| Code only in the same browser | Enter the 6-digit code in the browser where you requested the link. If you open the link on another device or in another browser (e.g. in the email app on your phone), the confirmation page warns you – if you confirm anyway, you are signed in there | By design (1.1.57); type the code from the email on your computer |
| Two-factor after the link | If you have 2FA turned on, we always ask for the code after the link – even on a device you chose to remember. “Remember this device for 30 days” only applies to signing in with a password | By design (1.1.57) |
| Many links in a row | We send at most 3 links per address in 15 minutes and 10 per day. Beyond that the page still shows “Check your inbox”, but no email arrives | By design (1.1.57, protection against abuse); wait a while or sign in with your password |
| Self-hosted | “Email me a sign-in link” only appears once a system mailbox is set up | By design (1.1.57); turn it off with AUTH_MAGIC_LINK=off |
Sign in with Google (since 1.1.57)
| Item | Effect | Status / workaround |
|---|---|---|
| Linking by email link only in the same browser | If you confirm “Link your account?” with a link, it only works in the browser where you chose “Sign in with Google” | By design (1.1.57, protects against someone else's Google account); in another browser, enter the code from the email |
| Two-factor after Google | If you have 2FA turned on, we always ask for the code after signing in with Google. “Remember this device for 30 days” only applies to signing in with a password | By design (1.1.57) |
| Linking only when signing in | My profile has no “Connect Google” button – you link by signing in with Google once. You can unlink under My profile | Known (1.1.57) |
| Unverified Google address | If Google hasn't verified the address, signing in with Google doesn't work | By design (1.1.57); use “Email me a sign-in link” |
| Self-hosted | “Sign in with Google” is off by default and needs your own Google project | By design (1.1.57); GOOGLE_OAUTH_CLIENT_ID, GOOGLE_OAUTH_CLIENT_SECRET, AUTH_GOOGLE=on |
Email: recipients, Cc/Bcc & forwarding (since 1.1.58)
| Item | Impact | Status / workaround |
|---|---|---|
| Emails from before 1.1.58 | No To/Cc is stored for them: “Reply” goes to the conversation's address there, “Reply all” without Cc | Known (1.1.58); add recipients above the reply box by hand |
| Intake via the email webhook | Only stores the sender, no To and no Cc | Known (1.1.58) |
| Forwarding | Only works from email conversations | Known (1.1.58) |
| New emails | New emails (“＋ New chat”) still go without attachments | Known (1.1.58); attachments work when replying and forwarding |
| Search | Search doesn't find conversations by Cc addresses | Known (1.1.58) |
| Limits of email providers | We don't know how many recipients and how large emails your provider accepts. If it refuses, the email shows “not delivered” | Known (1.1.58); at most 20 recipients per email, use a campaign for more |
| Cc people without a contact | “Delete contact permanently” only finds them once you've added them with “＋ Contact”. Addresses in the email text or quote stay | Known (1.1.58) |
Campaigns: counting opens and clicks (since 1.1.58)
| Item | Impact | Status / workaround |
|---|---|---|
| Counting only if you want to | Campaigns only count opens and clicks when “Count opens and clicks” is on (default off). Existing campaigns are set to “off” too; earlier numbers stay visible (“counted earlier”) | By design (1.1.58); only turn it on if your recipients have agreed to being counted |
| Links in old emails | If the link of an old email is no longer exactly in the campaign text, it shows “Invalid link” | Known (1.1.58) |
| Campaign turned off | Links in old emails of a campaign that is now turned off still lead to the destination, nothing is counted | By design (1.1.58) |
Self-hosted: phone system from the installer & home network (since 1.1.58)
| Item | Impact | Status / workaround |
|---|---|---|
| Update to 1.1.58 | Arrives via :latest (since 6 November 2026). Four small database changes run on start, no new setting. Worker and app belong together | Known (1.1.58); update.sh updates both. Steps in the release notes |
| Signing in over http in your home network | Phone in the browser, video, push, adding the app to your phone and some copy buttons only work with https; so does everything that needs a public https address (Meta, Telegram, Google sign-in, Microsoft 365) | Technical limit (1.1.58, browsers only allow this with https); for access from outside use a domain with https (guide) |
| Phone system from the installer: hold music | Without your own hold music the queue is silent | Known (1.1.58); upload your own music under Telephony → Music |
| Phone system from the installer: what's missing | The installer doesn't set up WhatsApp calls (own TLS port) or fail2ban for SIP. IPv4 only; no standby server with a phone system | Known (1.1.58); WhatsApp calls: guide |
| Phone system from the installer: updates | New Asterisk and coturn versions come with bash install.sh --add-phone, not with update.sh. Your own changes to pbx/asterisk/*.conf are replaced on update (the previous version is kept in pbx/.vorher/) | Known (1.1.58); your own parts belong in pbx/asterisk/include/ |
| Phone system from the installer: Docker networks | If your Docker networks are outside 172.16.0.0/12, the AMI account and the firewall (ufw) need one more line | Known (1.1.58); lines in SELF-HOSTING.md (German) → Telefonie |
Self-hosted: home network installation with the IP address (since 1.1.59)
| Item | Impact | Status / workaround |
|---|---|---|
| Update to 1.1.59 | Arrives via :latest (since 8 November 2026). One small database change (a new table for counters, empty for self-hosters) runs on start. Worker and app belong together | Known (1.1.59); update.sh updates both. Steps in the release notes |
| Links in emails over http/IP | If the installation runs over http:// with an IP address, links in emails and notifications only work inside your own network. Links for outside services (webhooks, Meta, images for social media) still need a public https address | Technical limit (1.1.59); set APP_URL exactly the way you open the app in the browser (with port). For access from outside use a domain with https (guide) |
Custom roles, security & integrations (since 1.1.60)
| Item | Impact | Status / workaround |
|---|---|---|
| Custom roles | There is no ready-made “Practice” template yet (doctor, assistant, front desk with one click), and roles can't be linked to teams or departments. Notifications to admins (e.g. payment reminders, mailbox problems) and report emails to admin and team lead only go to the standard roles, not to custom roles with the same permissions | Known (1.1.60); create roles yourself or copy a standard role (guide). Template and notifications by permission are planned |
| Giving permissions | You can only give permissions you have yourself – also when assigning a role and inviting. A team lead with “Manage roles” can therefore no longer create or invite an admin | Intended (1.1.60); an admin invites another admin |
| Old webhook signature | Besides X-TheY-Signature (with a timestamp) we still send the old X-KSCRM-Signature header (without a timestamp) so existing receivers don't break | Will be removed with version 1.2.0; please switch by then (verification example) |
| Own mailboxes in the cloud | Only connect to public mail servers on the usual ports (SMTP 25, 465, 587, 2525 · IMAP 143, 993). The CRM reports other ports or servers on a private network as an error | Intended (1.1.60); this limit doesn't apply when self-hosted |
| Webhooks to your own network (self-hosted) | Webhooks, action buttons and flows only call public addresses, also when self-hosted – not e.g. n8n on the same server or on your home network | Known (1.1.60); a switch for this is planned |
| Password pause | After 10 wrong passwords for an address, password sign-in is blocked for 15 minutes | Intended (1.1.60); sign-in by link or with Google still works |
Flows (automations)
| Item | Impact | Status / workaround |
|---|---|---|
| Trigger “Appointment coming up” | An appointment that is only created within the lead time, or moved into it, gets no reminder; neither does an appointment only on a deal without a contact | Known (1.1.58) |
| Old “Good rating → Google” flows | Keep running unchanged and only ask happy customers. Google doesn't allow that; the builder shows a notice | Known (1.1.58); switch to the template “Ask for a Google review after the conversation” |
| New flows and old rules | New flows are only created in the builder (“New flow”). Old simple rules still open with “Edit” (simple form) and “Builder”. The API still creates simple rules | By design (1.1.53) |
| Schedules per record | At most 500 records per run (default 100); those untouched the longest come first. “To the owner” means the person responsible for the contact | Known (1.1.53); “Recent runs” shows when the limit was reached |
| Trigger “Deal sits in a stage for X days” | Checked once a day. For very old deals the last change counts instead of the stage change | Known (1.1.53) |
| Overview and versions | “What runs automatically?” shows the state when the page was loaded; “payment reminders on” doesn't check whether a mailbox is connected. Versions have no name; the 50 newest are shown | Known (1.1.53) |
| Time in schedules | The time field is too narrow with a 12-hour browser clock (e.g. English/US). Browsers with a 24-hour clock are not affected | Known (1.1.53); fix planned |
| Not possible yet | “Wait for a reply, otherwise …”, form or webhook as a trigger, taking a webhook receiver's answer into fields | Planned; for “follow up if the customer doesn't reply” use the flow template “Customer doesn't reply for 3 days → follow up, then close”. An appointment as a trigger (“Appointment coming up”) exists since 1.1.58 |
| Limits on the Free plan | At most 5 active flows with up to 20 steps each, waits up to 30 days, log kept 30 days. Above the limit you can't switch on more flows | Existing rules stay active; saving as “Off” always works. Each automation pack adds +5 active flows; Cloud Pro and Paid: unlimited (1.1.41) |
| Marketing via SMS or WhatsApp | Only goes to contacts with explicit consent. SMS actions without a chosen purpose and WhatsApp templates in the “Marketing” category count as marketing. Pressing “1 for WhatsApp” only covers the callback | Intended (1.1.41); choose “Purpose: service” for service messages |
| Unsubscribed contacts | They only get automatic service emails in a conversation they started themselves. Anyone who opted out of SMS or WhatsApp gets nothing there | Intended (1.1.41) |
| Trigger “Key pressed in the phone menu” | The call is still running and there is usually no conversation yet — only contact actions work. With a withheld number there is no contact, so contact actions are skipped. Requires the built-in phone system | Known (1.1.41) |
| Time-based triggers | Checked every minute. After switching a flow on, only what becomes due afterwards counts. A schedule without records has no contact, so contact actions are skipped there | Known (1.1.41); since 1.1.53 a schedule can run “for every deal, contact or task” |
| Date as a trigger (record, deal, campaign) | Runs once a day at the time you set and only on the day itself. If the server was down for more than a day, missed days are not caught up. If the date is moved after sending, the reminder comes once more for the new date | Intended (1.1.42) – no late payment reminders |
| Never twice at the same time | If a rule is already running or waiting for the same conversation or contact, it doesn't start a second time there (e.g. two labels in the same second → one run) | Intended (1.1.41) |
| Test run | Assumes the data does not change along the way — e.g. “Add tag” in the test run doesn't affect later conditions | By design (1.1.41); nothing is sent, changed or saved |
| WhatsApp template in a flow | No separate path per template button yet. A freshly approved template can count as “not approved” for up to 5 minutes | Path per button planned; wait a moment after approval |
| Flow templates | “Appointment tomorrow → reminder” was not available yet. “Invoice 7 days overdue” points to dunning (Finance → Settings), which already sends payment reminders | ✅ “Appointment tomorrow → reminder” exists since 1.1.58: WhatsApp template, and if that doesn't work, SMS |
| Interrupted run | If a run is interrupted by a server restart, the log shows it as “Stopped (server restart)” and it is not repeated | By design — otherwise messages could go out twice |
| Trigger “Contact created” | Fires for every new contact – also for customers who write via WhatsApp, email, SMS, a call, Messenger or Instagram, or book online. A rule without a condition therefore runs much more often (e.g. a welcome message to every new contact) | By design (1.1.40); check your welcome rules and add a condition if needed |
| Email actions without a chosen purpose | Count as marketing and get an unsubscribe link | By design (1.1.40); set pure service emails (e.g. confirmations) to “Service” |
| Delayed rules | Conditions are not checked again when the actions run. If you changed the conversation by hand in the meantime, the rule overwrites it | Known (1.1.40) |
| Switching a rule off and on again | Switching off or deleting cancels waiting runs; switching back on does not catch up on them | By design (1.1.40) |
| Older rules with an empty condition value | Keep running as before and are marked “Condition without value” | Known (1.1.40); open the rule and pick a value |
| Protection against endless loops | The limit “same rule on the same contact at most 10 times in 10 minutes” only applies to rules with contact actions (email, WhatsApp, SMS, webhook, AI, deal …) | By design (1.1.35) |
| Action “Reply in conversation” in email conversations without a mailbox | The run reports “failed” instead of using the brand's only mailbox. Manual replies, “Send again” and the auto-reply use it since 1.1.51 | Known (1.1.51); connect a mailbox to the conversation or brand |
| Time limit per run | A run may take at most 60 seconds; webhook actions wait at most 10 seconds and read at most 1 MB | By design (1.1.35) |
AI features (your own AI key)
| Item | Impact | Status / workaround |
|---|---|---|
| Check and category estimate for WhatsApp templates | The rule check before submitting and "utility or marketing?" are estimates – Meta decides on the approval and category of a template. Without an AI key only a simple word check warns you | By design (1.1.43); templates are only submitted when you click |
| Translating templates | Each language is a separate template at Meta and is reviewed on its own. Quick-reply button texts differ per language – flows that check the button text then only match one language. An image or video header is uploaded again when submitting | Known (1.1.43); check flows with a button condition after translating |
| Explaining rejections | Not for code templates (sign-in codes), whose text Meta defines | Meta rule (1.1.43) |
| Flow from one sentence | New flows are always switched off. The AI only uses building blocks that exist in the builder; what isn't possible (yet) is shown in the result | Intended (1.1.43); check it, do a test run, then switch it on |
| AI step in flows | Runs in the background (a few seconds' delay), at most 2 at a time per account. It sends nothing itself and only takes values that literally appear in the message – never passport, ID or card numbers, dates of birth or health information. Without a key, when unsure or when the limit is reached, the flow continues in the "AI unsure" branch | Intended (1.1.43); in the "AI unsure" branch, notify a person or assign the conversation |
| Booking confirmation → trip | PDF up to 10 MB and 10 pages, text up to 20,000 characters; protected PDFs don't work. Your AI model must be able to read PDFs. Nothing is saved until you confirm; passport/ID numbers are never taken over, health information is never pre-filled | Known (1.1.43); if the model can't read PDFs, paste the text of the confirmation |
| Google as AI provider | Content from WhatsApp, Messenger and Instagram only goes to Google if the checkbox "My Google project has billing enabled (paid tier)" is ticked – also for translating, reply suggestions, summaries and classification in the inbox. The checkbox belongs to the key | Intended (1.1.43); enable billing in the Google project and confirm under Settings → AI; new key → confirm again |
| AI limits on the Free plan | 1,000 AI steps in flows and 300 extracted booking confirmations per month (documents that don't look like a trip don't count). Template AI and "From one sentence" have no monthly limit, only a brake against abuse | Counters under Settings → AI; Cloud Pro and paid licence: unlimited (1.1.43). You pay the AI costs directly to your provider |
Industry pack, trips, tools & import
| Item | Impact | Status / workaround |
|---|---|---|
| "Travel agency" industry pack | Applies to Austria and Germany. Its content (fields, quick replies, draft templates, sample data) is in German, also with an English interface (applied in Turkish, quick replies and reminders are in Turkish since 1.1.60). "Apply again" only adds what is missing; changed texts and stages are not overwritten | Known (1.1.42); all flows from the pack start switched off, you submit the draft templates yourself |
| Notes on payment rules (trips) | Notes only, not legal advice. Only package holidays are checked, under Austrian or German rules; flight-only, hotel-only, car hire and direct collection get no payment notes. Nothing is ever blocked | Intended (1.1.42); compare due dates with the tour operator's confirmation |
| Limits on the Free plan (1.1.42) | 300 running trips (finished trips don't count), 15 reminder flows from the pack in addition to the 5 flows, 15 enabled tool links (since 1.1.46 disabled ones don't count). Above the limit you can't add or enable more | What exists stays; Cloud Pro and your own server unlimited |
| Tool links | Open in a new tab; since 1.1.47 you can set per link that it always opens in the same tab. Only http/https addresses. In the inbox, deal values are only filled in if a deal is linked to the conversation. "Insert into chat" only inserts the address; for WhatsApp the 24-hour window still applies | Known (1.1.42) |
| Tool links “in the same tab per system” | Only works while the opened tab stays connected to the CRM tab. So only switch it on for systems you trust: the opened system could redirect the CRM tab to another page, it cannot read anything. If you work in two CRM tabs, each one gets its own tool tab | By design (1.1.47); the default stays “In a new tab” |
| CosmoNaut | On the first click you have to sign in to CosmoNaut and then click again. Right after signing in, CosmoNaut shows its default values; only the second click fills in the details. After that every search opens in the same tab. Reloading signs you out of CosmoNaut | Up to CosmoNaut (1.1.47); use the templates in version 2 (existing links show “New version of the template available”), under “Open” don't pick “reload every time” |
| CSV import with matching | The dry run changes nothing and starts no flows. Dates in US format (MM/DD/YYYY) and Excel serial numbers are not recognised. At most 5,000 rows per import; the column mapping can't be saved yet | Known (1.1.42); export dates as DD.MM.YYYY or YYYY-MM-DD |
| Turkish values (booking engine, payment rules) | The booking engine and the notes on payment rules understand the Turkish values from the selection lists of the demo (e.g. “Her şey dahil”, “Viyana”, “Paket tur”). The booking engine leaves other spellings empty, as with unknown German values | Known (1.1.48); use the values from the selection lists |
| Offer links | Only addresses you enter are recognised, and only in sent or received messages (not while typing) | Intended (1.1.42) |
| Managing pipelines | Stages that contain deals (including the bin) can't be deleted. Only empty pipelines can be deleted, never the default pipeline | Move deals in the Kanban first (1.1.42) |
Finance
| Item | Impact | Status / workaround |
|---|---|---|
| No tax advice, no submission | The VAT overview and the VAT basis settings only control the preview; nothing goes to FinanzOnline or ELSTER | By design; you or your tax advisor file the VAT return |
| VAT special cases | Partial supplies, the Swiss net tax rate method, input VAT restrictions, import VAT, foreign currency and the timing of EC sales lists are not calculated separately | Known (1.1.25); check with your tax advisor |
| Months closed before 1.1.25 | No saved VAT overview figures to compare with | Known (1.1.25) |
| Month-end close | Final — even support cannot reopen it | Corrections in the open month via credit note or reversal (1.1.23) |
| Payment reminders | The reminder fee only appears in the text; the reminder text can be copied, but is not available as a PDF yet. Automatic dunning only works with your own mailbox | Known (1.1.22, 1.1.40); dunning levels that went up without sending before 1.1.40 are not reset |
| E-invoice output | Output as XRechnung and Swiss QR-bill; ZUGFeRD/Factur-X not yet | Planned (Feature Board) |
| Bank | No direct bank connection | Upload the bank statement as camt.053 or CSV |
| DATEV and BMD export | Test once with your tax advisor before first real use | Note since 1.1.22 |
| Cancelled invoices with payments (older data) | Invoices cancelled despite a payment before 1.1.40 stay as they are | Check the VAT overview for those months (1.1.40) |
| Drafts with an invalid currency | Older drafts with an invalid currency (e.g. “€”) can only be issued once you pick a currency from the list | Known (1.1.40) |
Other product limitations
| Item | Impact | Status / workaround |
|---|---|---|
| Accessibility | Some select and number fields in the inbox (priority, assign), in campaigns and in the booking link form are not linked to their label for screen readers. The bell icon has a different name than its text. The conversation list can't be scrolled with the keyboard | Known (already before 1.1.58, checked with axe); the contrast findings in the inbox and on the booking page are fixed in 1.1.58 |
| Appointments on the dashboard | “Upcoming appointments” showed one hour early, as did times in “My calls” and the trash | ✅ Fixed in 1.1.58: in your account's time zone |
| Formats in the English and Turkish interface | In Workplace (shift plan, time tracking), custom objects, search and history, dates and numbers are partly still in the German format | Known (1.1.59); finance, invoices and the report follow the interface language since 1.1.59 |
| Settings | For single search words, side matches appear further down. “Snippets & email templates” takes two lines in the sidebar. The “Save changes” bar exists only on “Logo & colours” so far. The industry pack still says “quick replies”. New accounts still call the team lead role “Supervisor” in “Team & permissions” and in the invitation | Known (1.1.53); names will be aligned |
| Sections in the sidebar | New accounts start with inbox, contacts, deals, tasks, calendar, snippets and knowledge; team chat, finance, marketing, reports, comments and workplace are hidden. Hidden sections stay reachable via links and search. “Calls” also appears without a phone line | By design (1.1.53); show them under Settings → Sections (guide) |
| Inbox search | Message text from 3 characters and only within the first 4,000 characters of a message, without matching umlauts or typos. Attachments and the markup of HTML emails are not searched. Phone numbers from 5 digits. “Search all conversations” counts up to “100+” | By design (1.1.53); search more precisely |
| Inbox: mailbox and channel | The “Mailbox” filter, the channel buttons and the view on phones are not remembered and are not part of saved views. A newly connected mailbox appears in the filter only after reloading. WhatsApp and SMS with only one number show no “to …” line | Known (1.1.53) |
| Inbox for teams | @mentions show up in the bell and by email, not yet as a push. People with the same name are both notified. “Looking” and “typing” only cover replies to the customer, not notes. An appointment from a conversation sends the customer no invitation or reminder. The “e” key closes without asking | Known (1.1.53); push planned. Add the customer as an attendee in the calendar if needed |
| Opening hours (one for everything) | In existing accounts, channels that never had hours saved show “No hours so far” (closed, as before). “Take over opening hours” only replaces the times of the phone hours. If the holiday list is empty, the phone uses the public holidays of Austria or Germany, the automatic reply and response times do not. Time zone names come from the browser | By design (1.1.53); “Set all to ‘Like opening hours’” (guide) |
| Company: language and form of address | German-language accounts with the default survey text and formal address switched off now send the customer survey in the informal form (before: always formal). The account language applies to all automatic texts to customers without a known language, including WhatsApp notes from the phone system (not announcements). Changing the country under “Company” changes the default tax rate and chart of accounts if accounting is set up (you are asked first) | By design (1.1.53); switch the formal address on or save your own survey text |
| Web chat visitors as contacts | Name, email or number from the chat are not verified; only unambiguous details are taken over. Until you merge them there are two contacts with the same address – an email campaign can then arrive twice, and which of the two gets a new email is not fixed. The note “Maybe the same person as …” only shows on the new web chat contact. After merging, the conversation list and header still show the name from the chat. If very many new visitors come from one address, conversations are created without a contact (spam protection) | Known (1.1.53); ask before giving personal information in the chat, then merge (guide) |
| Web chat page | The tab icon only shows your own account logo (paid plan), not the brand kit logo. The guides per website builder come without guarantee | Known (1.1.53) |
| Changing the account address | Previous addresses stay reserved for your account as long as it exists; at most 10 previous addresses and 3 changes in 24 hours. Emails already sent name the old address (it forwards). A “New password” link that was open before the change shows “Link invalid” afterwards. Not available when self-hosted | By design (1.1.53); open the link from the email again (guide) |
| “Powered by The-Y” and sender per brand | On the free plan, the booking page, video appointment and help center show the account's company name, not a brand yet. Without the brand kit, a brand's sender is used for campaigns with a brand, flow emails with this brand's templates and payment reminders – not yet for appointment, booking and survey emails or replies | Known (1.1.53); more to come |
| Email templates with images | Images only as PNG or JPEG up to 1 MB, no list to delete them yet. Many email programs only show images after a click. Preview and test email of “All brands” templates use the default brand's frame | Known (1.1.53) |
| Campaigns: pace and delivery | If the server stops exactly while an email is going out, that one email can arrive twice when the campaign continues. Microsoft 365 mailboxes send at most 20 campaign emails per minute. A rejected mailbox sign-in counts as “failed” instead of pausing. Birthday and date campaigns paused over midnight go out a day later. A new run after “Stop” goes to the whole segment again. SMS delivery reports are not evaluated | Known (1.1.53); check the mailbox's access details (guide) |
| Team & permissions: role name | In Team & permissions and when inviting, the role is called “Team lead”; a few other places (e.g. role selection in flows) still say “Supervisor”. Custom or renamed roles keep their names | Known (1.1.53.1); not yet aligned in 1.1.54 and 1.1.55, follows later |
| “2FA for everyone” | API keys (Settings → Integrations) belong to the account, not to a person, and keep working as before. Email or push notifications to devices that are already signed in continue | Intended (1.1.53.1) |
| Accounting exports | The tax advisor export, journal CSV and retention package also require the “Export contacts” permission. Custom roles with finance permissions but without it no longer see the export buttons; single invoice PDFs and receipts stay | By design (1.1.53); grant “Export contacts” |
| Channel status | Applies per account, not per brand: the hint “send yourself a test email to …” can name another brand’s address. SMS counts as “Running” as soon as the access details are entered. “New chat” also offers email mailboxes without access details | Known (1.1.52) |
| Getting started | “Test message” also counts replies whose delivery failed afterwards. In the demo test environment sample data isn’t marked as sample | Known (1.1.52) |
| Inbox on laptops | At 1366×768 there is little room for the history; since 1.1.53 the header also shows “to …” and “typing”. The snippet list (“/”) isn’t filtered by brand. The “Closed” and “All” counters update up to 30 seconds later | Known (1.1.52); a more compact header is planned |
| Brand per conversation | A conversation can now only be moved to the brands of its mailbox or number (before: any brand) | Intended (1.1.52); add other brands on the channel as “additional brand” |
| Brand kit | Booking emails use the default brand for now. Campaigns use the brand’s first language. Personal details in {{signatur}} stay empty in flow emails. SMS templates don’t have a starting structure yet. The style check is a hint, not a reliable detection | Known (1.1.52); more to come. Since 1.1.53 the sender per brand also works without the brand kit |
| Translate in the demo | “Translate” only showed “Translation failed.” in the demo | ✅ Fixed in 1.1.47; in the demo at most 2,000 characters per text and 30 translations per minute |
| WhatsApp calls | Calls dropped after about 2 seconds (order of audio formats) | ✅ Fixed in 1.1.45.1 |
| Softphone ringtone | In some cases ringing continued after answering | ✅ Fixed in 1.1.45.1 |
| Inbox while loading | While loading, the inbox briefly showed all tickets instead of only the open ones; the ticket opened as a tab was sometimes a closed one | ✅ Fixed in 1.1.45: the first list is already filtered to “Open”, the counters are right immediately |
| Times on deal, contact and company pages | “Created” (on deals also “Closed”, on contacts also the conversation dates) was shown in UTC, i.e. 2 hours early | ✅ Fixed in 1.1.45: in your account's time zone (since 1.1.53 under Settings → Company) |
| SMS | No delivery reports; no confirmation SMS on “STOP” | Receiving replies works since 1.1.22 via the receiving address (guide) |
| WhatsApp/SMS campaigns | Existing contacts without recorded consent get no campaigns | Intended (1.1.22); record consent on the contact or via CSV |
| Customer replies reopen conversations | Applies to WhatsApp and SMS. Messenger and Instagram: unchanged. Replies to campaign messages start a new conversation once the period has passed | Since 1.1.41; period (default 7 days) under Settings → Opening hours & holidays |
| App on your phone | Push notifications are available as a beta since 1.1.50 (switch them on per device under “My profile” – in the menu under your name). On iPhone and iPad only in the installed app, iOS/iPadOS 16.4 or later. No key tones (DTMF) during a call | Push: beta (1.1.50); key tones planned (Feature Board) |
| Microsoft 365 / Outlook.com | In many companies a Microsoft 365 admin has to approve the app once. For sending, “Authenticated SMTP” must be allowed for the mailbox. After restoring a backup, click “Reconnect” once | Known (1.1.50); the app shows the link for your admin. Self-hosted, the button only appears with your own app registration at Microsoft |
| Gmail | You connect Gmail with an app password, not with one click. Google only offers app passwords with 2-Step Verification; some Google Workspace admins block them | By design (1.1.50); the setup explains the steps (guide) |
| Email after a mailbox or server move | At most the last 30 days are re-read; older emails on the new server do not arrive. Emails without an identifier (Message-ID) may appear twice | By design (1.1.51) |
| Very large emails | Emails over 40 MB only appear as a notice in the conversation; if an attachment cannot be stored, the file stays in the mailbox. Mailbox health lists emails that could not be imported | By design (1.1.51) |
| Metric “Ø first response” | Since 1.1.51 escalation and the SLA first response count from the customer's first message. The metric “Ø first response” in reports and “First response: …” in the ticket still count from when the conversation was created, so they looked too long for conversations you started | ✅ Fixed in 1.1.60: “Ø first response” in reports and “First response” in the ticket now count from the customer's first message, like escalation and SLA |
| Setup tips by email | You choose “No setup tips by email” when signing up. There was no switch for it in the app | ✅ Fixed in 1.1.60: admins switch it on or off under “My profile” (cloud only) |
| Signing out | Signs you out of all workspaces in this browser | Intended (1.1.25) |
| Demo / test environment | Runs for 24 hours, then everything is deleted; at most 3 per connection and day, 5 MB of files | Sign up for free to work permanently |
| Demo in Turkish | If you started the demo in Turkish, you got German sample data | ✅ Fixed in 1.1.48: Turkish travel agency “Demo Seyahat” from Vienna, also in the “Sadece görüntüle” (view only) sample company |
| Turkish demo: travel agency pack | Stages, trip fields and trips are in Turkish. Quick replies and reminders of the travel agency pack were only in German | ✅ Fixed in 1.1.60: applying the travel agency pack in Turkish gives you Turkish quick replies and reminders. The pack's pipeline, fields, WhatsApp drafts and sample data stay in German for now |
| Turkish interface: form of address | Apart from the demo pages, the Turkish interface still partly addressed you with “sen” | ✅ Fixed in 1.1.49: notices, error messages, emails and settings consistently use “siz”. Short buttons such as “Kaydet” stay as usual in Turkish software; older system notes in a conversation's history stay as they were saved |
| Turkish interface: new texts from 1.1.54 | Some new texts on the video page (e.g. the note before sharing your screen, which guests see too) and for booking links still addressed you with “sen” instead of “siz” | ✅ Fixed in 1.1.60: the video page and booking links use “siz” |
| Language of the demo sample data | If you switch the language inside the demo, the sample data stays in the language you started with | Intended (1.1.47); start the demo in the language you want |
| Security log without search/filter/export/pagination | Limited traceability | ✅ Shipped in 1.1.60: search, filters for time range, person and type, pages; admins download the log as CSV |
| API keys without scopes/expiry/rotation | Coarser access control | ✅ Shipped in 1.1.60: permissions per key (read contacts / create and update contacts), expiry date, renewal with a grace period; existing keys keep full permissions until you set them (guide) |
| Registration/contact form | Not fully accessible throughout (labels/required fields) | Improvement planned |
| Drafts in the inbox | Unsent text stayed in place, but was lost when you reloaded the page | ✅ Fixed in 1.1.60: unfinished replies, notes and email recipients survive a page reload. They stay only in your browser and are removed when you send, sign out, or after 7 days |
| “New chat” via WhatsApp or SMS (before 1.1.40) | Conversations started earlier with a number without country code are not rewritten; replies to them may land in a new conversation | Known (1.1.40) |
| WebChat on websites that block browser storage | The WebChat can't send there; the visitor sees “Not sent” | Known (1.1.40) |
| Contacts merged before 1.1.40 | The trash shows “N open meetings” | Move these meetings by hand before deleting for good (1.1.40) |
| CSV import: numbers imported earlier | Are not rewritten to the international format | They are still found when matching (1.1.40) |
| Meetings on the contact page | The invitation only went to the participants, not automatically to the contact | ✅ Fixed in 1.1.60: the contact is already added as a participant and gets the invitation (can be removed). A meeting created from the inbox doesn't add the customer yet |
| Older campaigns without date field, brand or text | No longer send since 1.1.40; you see the reason when you open or send them | By design (1.1.40); complete the campaign |
| WhatsApp campaigns: language | A campaign uses one language version of the template for all contacts | Known (1.1.40) |
| User limit and invitations | Open invitations count towards the user limit. Accounts already over the limit keep their users; only new invitations are blocked | Known (1.1.39) |
| Logo as SVG | Previously uploaded SVG logos are replaced by your initials | Upload your logo again as PNG, JPG or WebP (1.1.39) |
| Backup (snapshot) | Files (attachments, receipts, invoice PDFs, recordings) are not included. After “Reset” and restore, the “Sales” pipeline exists twice | Known (1.1.40) |
| Translation on our server | Only German, English and Turkish; Croatian, Serbian and Bosnian are not available there at all. Short chat sentences work well, idioms are sometimes inaccurate; Turkish↔German goes via English | Intended (1.1.42); for other languages or important replies choose your own AI or DeepL key (Settings → AI → Translation). Below every translation you see what translated it |
| Self-hosted | Email intake via webhook needs INBOUND_EMAIL_SECRET; behind several proxies set TRUSTED_PROXIES or CLIENT_IP_HEADER; existing installations switch once to the new MinIO image | Since 1.1.39 / 1.1.35, see the self-hosting guide |
| Self-hosted: backup and phone system | Automatic updates only replace the images. The new backup.sh (checks the backup before old ones are deleted) and pbx/asterisk/modules.conf therefore do not arrive by themselves | Since 1.1.50; fetch both files manually (curl -fsSLO https://the-y.at/backup.sh; modules.conf: the-y.at/pbx/asterisk/modules.conf.txt), see SELF-HOSTING.md (German). Done for phone systems the installer sets up from 1.1.58: update.sh takes over the phone system's base files after every update. For phone systems set up by hand, this item still applies |
| Self-hosted: update to 1.1.52 | Automatic updates only replace the images. The new scripts from selfhost/, the COMPOSE_FILE line, the restricted database role, the backup before every update and extensions.conf/modules.conf don’t arrive on their own. Backups from before 1.1.52 don’t contain database permissions yet | Known (1.1.52, via :latest since 26 October 2026); one-time steps in SELF-HOSTING.md (German; scripts: https://the-y.at/backup.sh, /restore.sh, /restore-files.sh, /restore-test.sh, /app-rolle.sh; docker-compose.backup.yml: curl -fsSL https://the-y.at/compose-backup.yml -o docker-compose.backup.yml; phone system: the-y.at/pbx/asterisk/extensions.conf.txt, the-y.at/pbx/asterisk/modules.conf.txt), the backup before every update comes with switching to update.sh |
| Self-hosted: update to 1.1.54/1.1.55 | Arrives via :latest (since 3 November 2026) as one update. No new script, no new setting; the database adds what it needs on start, the phone system is set up again once automatically. If you run your own TURN server (coturn) for video meetings and blocked your own public IP there, remove that block – otherwise connections break when both sides are on mobile data or behind a router | Known (1.1.54); steps in the release notes |
| Self-hosted: update to 1.1.53 | update.sh, schluessel.sh and the new backup.sh/restore.sh don't arrive via automatic updates (one-time switch). docker-compose.self-host*.yml keep Watchtower. If an update fails, update.sh swaps the images back, not the database. The nightly schedule (03:30) can overlap with the daily backup. If the passphrase is lost, the protected key file is worthless. Without file storage (MinIO/S3) there are no images in email templates, and recordings stay in the spool | Known (1.1.53, via :latest since 26 October 2026); download update.sh, schluessel.sh, backup.sh and restore.sh from the-y.at (e.g. curl -fsSLO https://the-y.at/backup.sh), switching see Self-hosting operations → Switching from Watchtower to update.sh |
| Self-hosted: Microsoft via The-Y | Only available once we enable the service. Needs a licence key and an https address without a sub-path | Known (1.1.52); until then use your own Microsoft app |
| Self-hosted: status check | The public status check reports “degraded” (503) if the worker hasn’t reported for more than 5 minutes. Monitors will then alert | Intended (1.1.52) |
| Self-hosted: phone voice in 1.1.50 | Without the speech service “piper”, a simpler computer voice speaks in 1.1.50. From 1.1.51 there are no computer voices any more | Known (1.1.50); best record your announcements yourself right away |
| Self-hosted: Watchtower (installations from before 1.1.53) | Automatic updates only replace the images, not the compose file. If you installed without install.sh, the watchtower service may lack DOCKER_API_VERSION. New Docker versions then report “client version … is too old”, and updates stop arriving | In the template since 1.1.48; add two lines, see Self-hosting operations → Updates |
| Self-hosted: translation | Automatic updates only replace the images, not the compose file. Installations from before 1.1.42 therefore don't have the optional translation service yet; without it (and without your own AI or DeepL key as translator) the inbox hides the “Translate” buttons since 1.1.59 (before, translating said "not set up"). The service uses up to 0.9 GB RAM and ~0.6 GB disk | Since 1.1.42; extend the compose file, see Self-hosting operations → Translation |
Documentation
| Item | Status |
|---|---|
| Guides for 2FA/recovery, security log, API keys/webhooks, export/deletion & backup are added. Open: dedicated detail guides for calendar/booking, tasks and CSAT/SLA | Docs keep being aligned with the feature set |
Found a bug? Report it directly in the app via the feedback widget or at office@the-y.at. For security reasons we do not list unfixed security vulnerabilities here — only after they are fixed, in the Release Notes.