LINKERNO PRODUCT STATUS

Know what is available now, what needs account setup, and what is still being validated.

Know what is live, controlled rollout, or planned.

LINKERNO is built as one customer-operations layer rather than a disconnected list of AI features. The target flow is Call / Chat / Form → Understand → Customer Record → Follow-Up → Book → Convert. This page separates production capabilities from controlled rollout, Shadow mode, and future work so businesses know exactly what they can rely on.

How to read this pageAvailable means the capability is part of the current production system. Configured by account / Controlled rollout means it can be enabled only when the business, provider and readiness requirements pass. Shadow / Pre-live means LINKERNO can evaluate or prepare the action without representing it as a completed customer-facing action. Planned means it is not sold as live today.
AVAILABLE

AI Voice Front Desk

Production inbound-call handling for supported service businesses.

  • AI call answering and structured intake
  • Customer name, callback number, address when required and service request
  • Urgency and call-context capture
  • Summaries, call records and client-portal visibility
  • Business-specific instructions and supported call routing
AVAILABLE

Customer Records + Operational History

Calls and inquiries are organized into operational records so the business can see what happened instead of receiving another vague voicemail.

  • Customer and lead records
  • Call history and available evidence
  • Outcome tracking without treating an internal event as proof of revenue
  • Performance and follow-up outcome views where configured
CONTROLLED ROLLOUT

LINKERNO Web Chat

Website chat is available only after account-level readiness checks pass.

  • Approved business instructions and knowledge
  • Required customer/account readiness
  • Private widget configuration
  • Automatic return to Shadow if a critical readiness condition is lost
CONFIGURED BY ACCOUNT

SMS Recovery + Two-Way SMS

SMS workflows use account-level provider, consent and compliance gates. They are not assumed live for every customer.

  • Provider-independent SMS action path with Twilio support where configured
  • Inbound and outbound conversation records
  • STOP and related opt-out handling
  • Missed-lead recovery only when the account is Live and consent requirements are satisfied
CONTROLLED ROLLOUT

Native Calendar + Voice Booking

Eligible configurations can move from an appointment request to provider-confirmed booking while preserving conflict and concurrency protection.

  • LINKERNO Native Calendar
  • Short-lived booking offers
  • Atomic double-booking protection
  • A slot is not shown as confirmed until the configured booking path confirms it
SHADOW / PRE-LIVE

Spam Guard 2.0

LINKERNO can score likely spam using explicit call evidence, but it does not silently auto-block calls based on an unverified guess.

  • Likely-spam, review and normal classifications
  • Evidence-based review signals
  • No automatic blocking in Shadow mode
  • Human review path for uncertain calls
SHADOW / PRE-LIVE

External CRM Sync

The CRM outbox can prepare normalized customer records for supported external systems without pretending data was transmitted before a provider connection is verified.

  • Prepared sync records
  • Provider and readiness separation
  • No transmission claim until an external connector actually sends the record
PLANNED / VALIDATION

Broader Omnichannel + Multilingual Expansion

These capabilities remain validation work and are not represented as universally live.

  • Official WhatsApp Business messaging integration
  • Additional CRM, calendar and automation connectors
  • Broader production voice-language support after provider and QA validation
  • Expanded multi-location controls
  • Automatic spam blocking only after a safe and reviewable policy is validated

Why some features do not switch on automatically

Actions that affect customers or external systems depend on the business workflow, provider configuration, consent requirements, account readiness and verified outcomes. A requested booking is not a confirmed booking until the scheduling path confirms it. A prepared CRM record is not treated as transmitted until the external connector succeeds. A spam score is not the same as permission to block a caller.

Commercial promise: LINKERNO sells the result that is actually ready for the account, not a roadmap checkbox. When a capability is still Shadow, Controlled Rollout or Planned, the site should say so.

Status descriptions are intentionally conservative. Exact availability can vary by account, provider, configuration and rollout stage.