01
Sign in to your account
Registration temporarily unavailable
What to enter
Sign in and confirm the dashboard opens on widport.com itself.
Open configuration →Documentation · quickstart
From zero to a published widget.
Configure hierarchy, model, knowledge, and experience before installing one tag on your site.
02
Create organization, project, environment, and namespace
This hierarchy defines ownership and isolation. Create it in this order: Organization (company/team) → Project (site/product) → Environment (production, staging, or development) → Namespace (the widget knowledge boundary).
What to enter
Use stable names. Example: Acme → Website → production → support. Wait for ready; if partial_failure appears, reconcile the organization before continuing.
Open configuration →03
BYOK or Managed AI
Managed AI
You do not need to connect your own model key. Continue to create your deployment.
BYOK
Choose the environment, keep DeepSeek as default or select another provider, paste the API key, and test it. Status should become active/ready.
Provider costs are separate. Never put the key in your site's HTML.
Configure BYOK →04
Create a deployment and authorize domains
The deployment creates the public widget key and limits which sites may call the API.
What to enter
Choose the namespace, name it, and enter full origins with https:// and no paths. Separate origins with commas, semicolons, or new lines: https://example.com, https://www.example.com.
Open configuration →05
Enable automatic routing
IntentParse first selects the domain and then runs the specialized schema. The client does not need to choose one.
What to enter
Open Schemas and keep Automatic (recommended). Pin a schema only as an advanced override for a dedicated deployment.
Open configuration →06
Add knowledge
Register content the widget is authorized to use: documentation, FAQs, policies, and reviewed instructions.
What to enter
Under Knowledge sources, select a namespace and enter a name, HTTPS provenance URL, language, classification, and approved content.
Open configuration →07
Scan, review, and publish
Saving a source does not automatically make it evidence. A scan normalizes it and creates a candidate; human review controls what reaches GQueries.
What to enter
Run the scan, open Review queue, then approve and publish. Confirm it under Published memories. Revoking removes evidence from the index.
Open configuration →08
Configure the experience
Set appearance, capabilities, schema, policies, and human handoff. In auto mode, the widget inherits the host site's light/dark theme and accent.
What to enter
Review every tab. Keep require evidence enabled for factual answers; configure fallback/handoff and enable only actions your backend supports.
Open configuration →09
Install the widget
Place the tag before </body> on every page where Widport should appear.
What to enter
Replace wp_pub_your_deployment_key with the public key shown in Deployments. Adjust data-locale and data-position; never put a BYOK secret in HTML. The closed launcher may visually shake for 3 seconds every 10 visible seconds. Use data-attention="off" to disable it for the site, or the widget control to disable it in this browser. Reduced motion always disables the animation.
<script
src="https://cdn.widport.com/v1/widget.js?v=1.5.1"
data-project="wp_pub_your_deployment_key"
data-locale="pt-BR"
data-position="bottom-right">
</script>10
Test end to end
Open your site on an authorized origin and ask both covered and uncovered questions.
What to enter
Covered answers should cite evidence. Missing evidence should trigger clarification or human handoff. Monitor Journeys and Usage.
Open configuration →Google Calendar
Prepare your booking flow. The integration is not available yet; this page does not query calendars or create events.
Planned setup
- Offer human support
First, ask whether the person prefers to book with a human agent.
- Show availability
If they choose automatic booking, the planned flow will check and show available times once the integration is implemented.
- Confirm the time
The event should only be created after the person explicitly confirms the time, once the integration is available.
For now, arrange bookings with a human agent outside this integration. There is no Google Calendar field or working OAuth connection: do not paste keys, tokens, or secrets.
View Calendar status →Set up your team.
Collaboration within one organization, with access by role and scope. Teams is not available yet; these are the planned settings.
Prepare your setup
- Identify the organization
The owner will choose the organization and identify who needs to collaborate, without sharing their account.
- Choose a role and scope
Plan the minimum access needed. Limit projects, channels, and queues; a role does not unlock other organizations.
- Review before inviting
The planned flow will require an owner invitation and explicit acceptance with a verified email. Invitations and permission management have not been implemented yet.
Planned roles
Owner
The organization owner. Defines members, roles, and scopes; not the platform's global administrator.
Operations manager
Manages resources, knowledge, and support within the authorized scope.
Operator
Handles conversations and their own tasks within the permitted scope.
Observer
Reads information within scope, without making changes or replying to conversations.
Finance
Reads billing, usage, and financial audit data; cannot access conversations or credentials.
The tasks and permissions described here are part of the Teams plan. Changing the owner will be a separate flow, not a role edit.
View Teams planning →