LINKERNO TRUST CENTER
Know what LINKERNO does, how it is used, and what remains under your control.
LINKERNO answers customer inquiries and can prepare or execute business actions only when the relevant account, provider, consent and readiness conditions are satisfied. We separate a request from a confirmed outcome and a prepared action from a completed external action.
LINKERNO is configured around approved business information such as services, hours, service area, caller questions, escalation rules and things the AI should never promise. Customer-facing automation should use approved knowledge rather than inventing business policy.
Customer-facing channels and external actions can be gated by account status, provider health, business instructions, consent, knowledge approval and other capability-specific checks. Losing a critical readiness condition can return a capability to Shadow instead of continuing blindly.
Shadow means LINKERNO can evaluate or prepare an action without representing it as completed. Controlled Rollout means a capability is enabled only for eligible configured accounts. Live means the approved customer-facing path can execute. The current status of major capabilities is published on the Product Status page.
An appointment request is not a confirmed appointment. LINKERNO should show a booking as confirmed only when the configured calendar or scheduling path actually confirms the slot. Booking flows include conflict and concurrency protections where supported.
SMS recovery and related messaging depend on the applicable account, provider and consent requirements. Inbound STOP and related opt-out keywords are handled as opt-outs in the supported SMS path. A configured provider alone does not mean customer-facing messaging is automatically enabled.
Spam Guard can use explicit call evidence to classify likely spam, review or normal calls in Shadow mode. A score is not treated as permission to silently block a customer. Automatic blocking remains separate from evidence collection and review.
LINKERNO can prepare normalized customer information for CRM synchronization. A queued or prepared record is not described as transmitted until a supported connector actually sends it successfully.
LINKERNO can record operational outcomes such as answered calls, follow-up events, replies and confirmed bookings. Internal events are not automatically treated as proof of booked revenue. Revenue claims should remain tied to evidence the business can verify.
LINKERNO is built around organized customer intake and operational records. Access should be limited to authorized business users and configured providers. We do not claim security, privacy or compliance certifications unless they are specifically documented by LINKERNO.
AI should support a business front office, not hide important edge cases. Safety-sensitive, emergency, legal, medical, financial and other high-risk situations should follow the business’s human escalation rules and applicable professional requirements.
Businesses are responsible for using LINKERNO in a way that follows applicable calling, recording, consent, privacy, messaging and industry rules. Requirements can vary by location and use case. Businesses should configure disclosures and workflows appropriate to their operations and obtain legal advice when required.
LINKERNO publishes current plans, included usage and overage terms on the website. One-time implementation, website and integration work is scoped separately. We prefer specific, testable claims over promises that cannot be verified, and we do not represent Controlled Rollout, Shadow or Planned capabilities as universally live.
Read the current Privacy Policy, Terms of Service and Product Status. For product, privacy or trust questions, email info@linkerno.com.