Does every channel use the same knowledge?
Yes. Connected channels can use the same agent instructions, FAQs, files, website sources, products, rules, and configured actions.
Seven customer channels. One workspace.
Every channel.One conversation.
Connect the places customers already message you. Keep the knowledge, rules, actions, and handoff in one operating layer.
Shared knowledgeChannel-aware inboxHuman takeover
B
Routing liveChannel switchboard
Northstar Goods · live traffic
Nabila Rahman
WhatsApp · 10:24
Today, 10:24
Do you have the Forest Runner in size 42?
Message received from WhatsApp
BoundBot answer
Same knowledge · channel-ready format
Yes — size 42 is available. We have 9 pairs left at ৳3,850.
SourceProduct catalog
Ready to sendOne inbox
01Receive
02Ground
03Route
WebChat
Messenger
Telegram
Slack
Discord
One agent at the center
Configure once. Adapt at the edge.
Your business truth stays centralized. BoundBot turns it into the right response format for each connected channel.
Same knowledge
No separate FAQ brain for every channel.
Same rules
Keep routing and escalation behavior consistent.
Same visibility
Review every thread in one operational inbox.
Shared agent core
One configuration · every connected edge
Knowledge
FAQs · products · policies
Agent instructions
Voice · limits · priorities
Rules and actions
Triggers · tools · handoff
Messenger
WebChat
Telegram
Slack
Discord
128
Knowledge items
12
Rules
7
Channels
Channel atlas
Pick the entry points that matter.
Start with one channel. Add the rest without rebuilding the agent behind it.
Each provider keeps its own account, permission, delivery, consent, and policy requirements.
Your storefront
WebChat
Launch a branded widget on your site and route every thread into the shared inbox.
Mobile commerce
Answer customer-initiated questions with approved knowledge and a clear human path.
Facebook Pages
Messenger
Bring Page conversations into the same knowledge, inbox, and handoff workflow.
Social conversations
Keep Instagram-originated customer conversations visible beside your other channels.
Fast mobile support
Telegram
Run quick support and community flows through a connected Telegram bot.
Team operations
Slack
Bring grounded assistance into the workspace where your internal team already works.
Product communities
Discord
Handle community questions with shared knowledge and a consistent agent identity.
Browser sidekick
Chrome extension
Open BoundBot in a browser sidebar to test, demo, and work without switching tabs.
WhatsApp support
Helpful by default. Human when needed.
Ground customer-initiated conversations in approved business knowledge, capture only useful details, and keep the team close.
Answer from FAQs, policies, and products
Capture contact details with conversation context
Pause automation and hand the thread to a person
Northstar Goods
Typically replies instantly
Today
Can I change the delivery address?
I’ll bring in a teammate so they can update it safely.
Human handoff
Nadia is joining
Conversation context included
Reply…
Platform boundary
Meta account setup, consent, eligibility, and template rules still apply.
Northstar Goods
Facebook Page inbox
RH
Rafi Hassan
Delivery outside Dhaka?
Messenger
SA
Sadia Ahmed
Need help choosing a size
Messenger
MK
Mehedi Khan
Where is my order?
Messenger
Rafi Hassan
Messenger · active now
Can you deliver outside Dhaka?
Yes — delivery is available nationwide. Timing depends on the destination.
Delivery FAQ
Grounded source Messenger support
Your Page messages. Your same support brain.
Route inbound Facebook Page conversations through the knowledge, history, and team workflow already running elsewhere.
What stays consistent
Approved knowledgeLead contextConversation historyHuman takeover
Requires an eligible Facebook Page, Meta permissions, webhook configuration, and compliance with current messaging policies.
Read Messenger setupOne queue for the team
Never ask, “Which app was that in?”
Every thread keeps its channel identity while the team works from one conversation view.
Context survives the handoff
The customer question, channel, history, and agent response stay in the same thread.
B
12 openAll conversations
One queue · every channel
NR
Nabila Rahman
Can I change my address?
RH
Rafi Hassan
Delivery outside Dhaka?
TA
Tanvir Ahmed
I need the blue version.
SA
Sadia Ahmed
Can someone help?
Nabila Rahman
WhatsApp · active now
Can I change the delivery address?
Nadia is joining to update it safely.
Human handoff
Nadia joined
Full conversation context
A controlled launch
Connect. Test. Then automate.
Every channel rollout follows the same four checks, even when provider setup differs.
- 01
Connect the account
Authorize the channel and complete the provider setup it requires.
- 02
Choose the agent
Use the same instructions, knowledge, rules, and actions across channels.
- 03
Test the route
Send a real message and confirm the answer, source, and inbox thread.
- 04
Open the inbox
Give the team a clear takeover path before automation goes live.
Integration questions
Know the boundaries before launch.
The agent layer gets simpler. Provider rules still deserve a careful setup.
Can my team see which channel a message came from?
Yes. Conversations stay channel-aware in the shared inbox so the team can see the source and continue with the right context.
Does BoundBot replace Meta or channel approval rules?
No. Account eligibility, permissions, consent, templates, delivery windows, and other platform requirements still come from each provider.
Can a person take over the conversation?
Yes. Configure human handoff, pause automatic replies, and let a teammate continue from the same conversation history.
Start with one channel. Keep room for every next one.