PhiSo

PhiSo is the visitor surface operator. Every published Surface ships with a PhiSo widget that answers visitor questions from the live Surface contract — the same blocks, copy, and capability data the visitor’s browser is rendering. No external scraping, no separate index, no extra training step.

PhiSo is the runtime counterpart to PhiCo: one authors, one answers.

What PhiSo reads

PhiSo’s knowledge is the Surface itself:

• Block contents — text, headings, button labels, table rows.
• Block manifest knowledge — each block’s 4-field brief (intent, whenToUse, whenNotToUse, commonMistakes) plus any per-World overrides the customer has configured.
• Capability config — what data sources are bound, what the navigation graph looks like.
• World-level context — public profile fields the World opts into.

PhiSo does not read private entity data, user records, billing information, or anything not part of the published Surface contract. Visitors interact with PhiSo authenticated through their PhiWebs account (no anonymous access).

Plan entitlements

PhiSo availability and quota follow your World’s plan:

Top up additional Φ from World settings → Billing if you hit the cap mid-month. The widget gracefully degrades to “ask later” when quota is exhausted, never to a billing error.

Configuring PhiSo

Open World settings → AI → PhiSo to:

• Toggle the widget per Surface.
• Customise greeting, tone, and refusal language.
• Pin a primary call-to-action (e.g. “Book a demo”).
• Configure escalation handoff (email, Slack via the connector).
• View per-Surface metrics: question volume, deflection rate, Φ spend.

Refusing and escalating

PhiSo refuses when:

• The question asks for information outside the published Surface contract.
• The question violates a tenant policy you configured.
• The question targets private World data PhiSo can’t see.

When refusing, PhiSo offers the configured escalation path. Escalation turns are still charged against your Φ grant.

Caching and freshness

PhiSo answers from the live Surface — there is no separate retrieval index that needs warming. After a publish, expect up to 5 minutes for edge caches to clear before the new content reaches every visitor’s PhiSo widget.

If the Surface contract doesn’t expose a field PhiSo is being asked about, the answer will be a polite refusal even if the underlying data exists elsewhere. Surface the field (add a data block, expose it in a capability) to teach PhiSo about it.

API

Per-Surface metrics and effective config are surfaced in the World settings → AI → PhiSo UI; programmatic endpoints for them are planned.

See also

• PhiCo — the authoring composer
• AI integration — agent registry, model selection
• Surfaces — what PhiSo reads from