Skip to request-channel preview

LIMOCON TECHNOLOGIES

LT Google Review Booster

Back to local demo

Canonical V1 request-channel catalog

Request channels and completion trigger

Review the ten source-derived catalog entries by route class, product scope, consent and provider expectations, and supported placement or use case.

Local source-derived preview — no channel is activated

Catalog inclusion is not live availability. This page does not prove that any channel or trigger is enabled.

Plan scope never proves live entitlement, country availability, provider readiness, consent, sender or template approval, or feature activation.

Direct-message provider accounts and costs remain merchant-owned where applicable; LIMOCON TECHNOLOGIES does not activate or fund them from this preview.

This read-only local preview contains no customer data and performs no provider call, send, automation run, country activation, or purchase action.

Route class

Direct messages

direct_message

Email, SMS, WhatsApp, and Facebook Messenger require recipient consent and provider readiness before any production send.

email

Email request

Core and Growth product scope
Customer request or trigger
Emits a customer review request only after every independent production gate passes.
Recipient consent expectation
Required — Recipient consent is required before any production send.
Provider-readiness expectation
Required — Provider readiness is required before any production send.

Supported placements and use cases

  • Email deliveryemail_delivery

sms

Twilio SMS request

Growth product scope only
Customer request or trigger
Emits a customer review request only after every independent production gate passes.
Recipient consent expectation
Required — Recipient consent is required before any production send.
Provider-readiness expectation
Required — Provider readiness is required before any production send.

Supported placements and use cases

  • Twilio SMS deliverysms_delivery

whatsapp

WhatsApp request

Growth product scope only
Customer request or trigger
Emits a customer review request only after every independent production gate passes.
Recipient consent expectation
Required — Recipient consent is required before any production send.
Provider-readiness expectation
Required — Provider readiness is required before any production send.

Supported placements and use cases

  • WhatsApp deliverywhatsapp_delivery

messenger

Facebook Messenger request

Growth product scope only
Customer request or trigger
Emits a customer review request only after every independent production gate passes.
Recipient consent expectation
Required — Recipient consent is required before any production send.
Provider-readiness expectation
Required — Provider readiness is required before any production send.

Supported placements and use cases

  • Facebook Messenger deliverymessenger_delivery

Route class

Public request assets

public_asset

QR, NFC, print, on-screen QR, and manual short link present a neutral voluntary request, while destination, placement, entitlement, country, and server gates still apply.

qr

QR code

Core and Growth product scope
Customer request or trigger
Presents a neutral voluntary customer request only after every applicable gate passes.
Recipient consent expectation
Not direct — This route is not itself driven by a direct-recipient consent field; applicable downstream and server gates still apply.
Provider-readiness expectation
Not direct — This route is not itself a messaging-provider route; applicable downstream and server gates still apply.

Supported placements and use cases

  • QR codeqr_code
  • Receiptreceipt
  • Invoiceinvoice
  • Bill folderbill_folder
  • Cashier stationcashier_station
  • Receptionist stationreceptionist_station
  • Waiting areawaiting_area
  • Other authorized public displayother_authorized_public_display

nfc

NFC card

Core and Growth product scope
Customer request or trigger
Presents a neutral voluntary customer request only after every applicable gate passes.
Recipient consent expectation
Not direct — This route is not itself driven by a direct-recipient consent field; applicable downstream and server gates still apply.
Provider-readiness expectation
Not direct — This route is not itself a messaging-provider route; applicable downstream and server gates still apply.

Supported placements and use cases

  • NFC tapnfc_tap

print

Printed materials

Core and Growth product scope
Customer request or trigger
Presents a neutral voluntary customer request only after every applicable gate passes.
Recipient consent expectation
Not direct — This route is not itself driven by a direct-recipient consent field; applicable downstream and server gates still apply.
Provider-readiness expectation
Not direct — This route is not itself a messaging-provider route; applicable downstream and server gates still apply.

Supported placements and use cases

  • Printed materialprinted_material
  • Receiptreceipt
  • Invoiceinvoice
  • Bill folderbill_folder
  • Cashier stationcashier_station
  • Receptionist stationreceptionist_station
  • Waiting areawaiting_area
  • Other authorized public displayother_authorized_public_display

screen

On-screen QR

Core and Growth product scope
Customer request or trigger
Presents a neutral voluntary customer request only after every applicable gate passes.
Recipient consent expectation
Not direct — This route is not itself driven by a direct-recipient consent field; applicable downstream and server gates still apply.
Provider-readiness expectation
Not direct — This route is not itself a messaging-provider route; applicable downstream and server gates still apply.

Supported placements and use cases

  • On-screen QRon_screen_qr
  • Cashier stationcashier_station
  • Receptionist stationreceptionist_station
  • Waiting areawaiting_area
  • Other authorized public displayother_authorized_public_display

manual_link

Manual short link

Core and Growth product scope
Customer request or trigger
Presents a neutral voluntary customer request only after every applicable gate passes.
Recipient consent expectation
Not direct — This route is not itself driven by a direct-recipient consent field; applicable downstream and server gates still apply.
Provider-readiness expectation
Not direct — This route is not itself a messaging-provider route; applicable downstream and server gates still apply.

Supported placements and use cases

  • Manual short linkmanual_short_link
  • Receiptreceipt
  • Invoiceinvoice

Route class

Automation trigger

automation_trigger

A completion event records a bounded completed-service trigger only. A separately eligible downstream request channel performs delivery.

completion_event

POS/CRM completed-service automation

Growth product scope only
Customer request or trigger
Records a completed-service trigger only; a separately eligible downstream request channel performs delivery.
Recipient consent expectation
Not direct — This route is not itself driven by a direct-recipient consent field; applicable downstream and server gates still apply.
Provider-readiness expectation
Not direct — This route is not itself a messaging-provider route; applicable downstream and server gates still apply.

Supported placements and use cases

  • POS/CRM completed servicepos_crm_completed_service