Before you begin
You need:- a Dubot workspace and an Admin or Owner role;
- a safe product page for Test;
- a provisioned browser-extension Test session;
- the public client token and an approved product origin; and
- one customer question or task with an observable result.
The example you will build
Help a customer find the article Invite a teammate from your product’s team-settings page. Use your own public article and actual product path in place of this example. Success is simple: the Resource Center opens, its article card opens the right help page, and searching for invite returns that article. This first experience uses an article and Search. Leave Ask off until you are ready to configure and test its Agent.Build the first path
1
Connect a safe Test page
Install the browser SDK, or use a provisioned
browser-extension Test session. Confirm the target
page can load Dubot before configuring a larger experience.
2
Index one public article
In Knowledge, choose Crawl a URL, enter your public Invite a teammate article URL,
and select This page only. Open View articles after the crawl and confirm the title,
URL, and instructions. Knowledge is delivered automatically; there is no article Publish step.
3
Configure one Resource Center path
Open Resource Center. In Content, create an Exact
route override for your team-settings path, such as
/settings/team, and add the indexed
Invite a teammate article. Enable Search the knowledge base and leave Ask in your
own words off. In Settings, choose Floating so the customer can open the panel.4
Save and exercise Test
Save the Resource Center draft. From its Agent tab, start a browser-extension Test session
on your team-settings page. Open the floating panel, open the article card, then search for
invite. Confirm the search result has the expected title and destination. If your workspace
already has other sources, Search can return those articles too; route overrides organize
cards but do not limit Search to that page’s cards.
5
Publish the Resource Center
After the Test checks pass, select Publish on the Resource Center page. This example
needs no actions, Skill capabilities, or guides. If you changed Brand, publish those changes
as well. Saving a draft alone does not update the customer-facing panel.
6
Verify Production
End the Test session and load the same page with the installed SDK on an approved Production
origin. Repeat the card and Search checks, and confirm the Resource Center analytics record.
The extension alone does not install Dubot for your customers.
You are ready to expand when
- a representative customer can find or complete the intended job;
- Test and Production show the versions you expect;
- unavailable content or actions fail clearly;
- the result appears in the relevant Activity or Analytics view; and
- you know how to unpublish or recover the configuration.