AI and outbound communication rules
Current rule: Laborbot.si does not send email, SMS or voice calls and does not submit customer content to a model. Drafts, plans, approvals and demonstrations are internal records only; none is evidence that a message was delivered or that a recipient consented.
Last updated October 28, 2026. These rules document the current preview boundary. They are not approved legal advice or a claim that market-specific AI, marketing or electronic-communications requirements are complete.
AI disclosure
No model provider account, API key or model endpoint is connected. The public example is deterministic and runs without model generation. Laborbot does not currently send signup, contact or workspace content to a model and does not produce model-generated customer work.
The API-key destination remains paused. A future model connection requires a selected provider and approved endpoints, account-level training and sharing settings, retention, region and subprocessors, deletion and export behavior, contract and privacy approval, and retained verification evidence before activation.
Email rule
No customer email or marketing provider is connected. Early-access and contact submissions are stored for review; they do not trigger a confirmation, subscription, campaign, support reply, reminder or other outbound email. A prepared email or approved draft remains unsent until a separately tested provider delivery path exists.
SMS and voice rule
SMS and voice are not enabled or approved channels. Laborbot has no sending number, telephony provider, dialer, recorded voice, text campaign or delivery receipt integration. Those channels remain out of scope unless separately approved, configured and tested with market-specific consent and disclosure controls.
Stop signals and human takeover
Workspace owners and administrators can record a reply, opt-out, complaint or human-takeover signal for a contact reference. Any stored signal blocks the application's automated message authorization for that contact. Because no external messaging provider is connected, the control does not itself send a confirmation or prove provider-side suppression.
Required gates before any channel is enabled
- Verified business identity, launch markets, qualified legal review and an approved purpose and legal basis for the exact audience.
- Approved sender identity, domain or phone number; documented audience source and recipient opt-in evidence where required.
- Approved content and channel disclosures, quiet hours, frequency limits, unsubscribe or stop behavior and human escalation.
- Provider-side suppression synchronization, delivery and failure receipts, complaint handling and reconciliation tests.
- Selected provider contracts, data-processing terms, retention and region settings, incident duties and retained production evidence.
Until every applicable gate is approved and verified, the only safe interpretation is no outbound delivery and no model processing. See consent and communication choices, provider disclosure, privacy notice and preview use rules.