Service status
Sample metric
AI-powered Omnichannel Customer Experience Platform
Every Conversation. One Intelligent Platform.
Social, WhatsApp Business, web live chat, CRM, and voice in one workspace. The screen below is a sample — use the rail and cards to move through the product.
Sample data · click to explore
Channel summary
WhatsApp, sosyal, web, santral
Program summary
PostsPlannedCustomersMessagesAgents
Channel summary
FacebookInstagramWebWhatsAppBusinessTelegramLive
Quick access
Meta ads
Detailed filters
Is a sea-view room available tomorrow?Guest · sample
A standard sea-view room is free tomorrow. I can send a booking draft if you approve.AI draft
Choose a file first.
How many seats are left on this weekend’s Bodrum tour?Guest · sample
Four seats remain on Saturday. I can pass this to sales.AI draft
Where is my order?Customer · sample
The shipment is in transit. Should I send the tracking number?AI draft
What is the daily rate?Guest · sample appointment
Ready (ext. 1000)
Sample call log. This screen does not place a live call.
- Demo BeachInbound · 11:18 · 0242 255 07 62
- Ege TurOutbound · 10:42 · sales line
- Missed10:05 · 0555 010 20 30
1
2
3
4
5
6
7
Step 1 · Business
0 selected
Post type
| Title | Body | Action |
|---|---|---|
| Greeting | Hello from Demo Beach. How can we help? | |
| Dates and party | Which dates, and how many people? | |
| Availability | A standard room is open tomorrow. I can send a booking draft if you confirm. | |
| Transfer | What time should the airport transfer be? |
Early bookingSample template
Morning noteSample template
Demo Beach guestsSample list · 3 rows
No completed sample send. Drafts show up here.
Sample queue is empty.
Inbound Outbound New customer
| Account | In | Out | New | WhatsApp TR | WhatsApp other |
|---|---|---|---|---|---|
| Demo Beach | 6 | 4 | 2 | 3 | 1 |
| Ege Tur | 3 | 2 | 1 | 1 | 0 |
| Şehir Mağaza | 4 | 3 | 1 | 0 | 1 |
Figures are a sample. A live report uses the counts from the channels you connect.
| First name | Last name | Role | System | Actions | |
|---|---|---|---|---|---|
| Deniz | Kaya | deniz.kaya@ornek.otel | Agent | ||
| Ege | Usta | ege.usta@ornek.acente | Manager | ||
| Selin | Mart | selin.mart@ornek.magaza | Agent |
No note yet.
Room and price link is a sample. No live booking leaves this window.
Page mapping is a sample.
The bot replies only under the rule you turn on.
Sample room. No live price or booking is sent.
Standard room
2 adults · tomorrow · sample
2 adults · tomorrow · sample
Meta Tech Provider · Solution PartnerWhatsApp accounts, templates, and messaging connect through the WhatsApp Business Platform.
Main features
Every channel on one screen
WhatsApp, Instagram, Facebook, Telegram, web live chat, and phone gather in one inbox. The team sees the message, replies, and hands a complex request to sales or support.
An AI draft, under your rule
Frequent questions get a reply draft. Automatic sending runs only in the case you define. A complex request goes to an agent, and what reaches the customer follows your rule.
WhatsApp Business operations
Lines, templates, and campaigns are managed from the channels screen. Image and template messages are prepared here. Sending depends on consent, template eligibility, and the platform rule.
Web phone and the switchboard
Calls are placed from the browser phone. The call stays beside the thread. The line and the extension open according to the switchboard you connect.
Customer card and sales follow-up
Channel, tag, language, and history stay on one record. A booking, order, or appointment request lands with the right team. Sales and support see the same customer.
Social and the inbox
The content plan, publishing, and incoming messages share one operation. Comments and direct messages land in the inbox. Images are picked from the media list.
Modules
The job you pick fills the panel.
Inbox
WhatsApp, social, web live chat, and phone gather in one queue. The team sees the message here, replies, and leaves it with the right person.
- One queueMessages and calls wait side by side. Channel, time, and who is looking stay on the same list.
- OwnershipYou can see who holds the thread. Waiting, active, and handed-off work stay distinct.
- HandoffSales or support takes the conversation from this screen. The record stays if the customer changes channel.
AI
Frequent questions get a draft. What reaches the customer follows your rule, and a complex request stays with a person.
- DraftRepeating questions about a booking, a price, or an order get a suggested reply. The agent sees the text before it goes out.
- LimitAutomatic sending runs only in the case you define. Without that rule, the message stays a draft.
- HandoffA complaint, an exception, or an unclear request goes to an agent. The history stays when ownership changes.
A customer’s WhatsApp thread lands in the inbox. The team answers it beside the other channels, without opening a separate app.
- ThreadThe message, the time, and the channel sit on the conversation card. The team replies from the same screen.
- Same queueIt appears beside Instagram, Facebook, and web requests. The customer record does not split when the channel changes.
- HandoffThe thread can move to sales or support. The person who passed it, and the new owner, stay visible.
Web phone
The switchboard call is placed from the browser phone. It stays beside the thread, so the team does not open another program.
- SwitchboardThe keypad, hold, and end sit on this screen. The extension opens according to the switchboard you connect.
- LineThe sample line shows the Demo Beach number. Which live number is connected is set during setup.
- Beside chatThe earlier thread stays visible during the call. When the call ends, the record remains on the same card.
CRM
Every conversation has a customer. Channel, tag, and history stay on one card, and sales sees the opportunity from here.
- CardName, channel, language, and tag sit on one record. A new message does not open a blank card.
- SegmentA booking, order, or appointment tag lands in the sales queue. An unrelated request stays with support.
- RecordThe thread and the call attach to the same customer. The team continues without asking for the history again.
Social
The publishing plan and incoming messages share one operation. Content is prepared, an image is chosen, and comments land in the inbox.
- PlanThe post calendar lives on this screen. When it goes out, and on which account, stay together.
- IncomingComments and direct messages drop into the inbox. Publishing and support see the same customer.
- FilesPhotos and video are picked from the media list. The same image can be used in a post and in a reply.
Direct messages and comments sit in the inbox with the other channels. The publishing plan stays on the social screen.
- MessageA direct message joins the queue with the sender and the time. In the sample, Ege Tur writes from this channel.
- CommentIncoming interaction does not scatter into a separate box. The team replies from the same operation.
- PublishingPosts and stories sit on the social calendar. The image is picked from the media list.
A page message lands in the inbox. An order or product question waits beside WhatsApp and web requests.
- MessageThe page thread joins the queue without a separate panel. The team replies from the same screen.
- OrderIn the sample, Şehir Mağaza writes from this channel. The request can be tagged and passed to sales.
- QueueFacebook waits in the same list as the other channels. The channel mark stays on the thread.
Telegram
A Telegram chat connects to the inbox. The team sees it beside the work from the other channels.
- ChannelThe message joins the queue with the time and the sender. There is no separate Telegram screen to open.
- TeamThe owner of the thread is visible. Waiting work and claimed work stay apart on the same list.
- HandoffThe request can move to sales or support. The history stays in front of the new owner.
Live chat
A request from the support window on the site joins the same inbox as the other channels.
- SiteWhen a visitor writes, the thread enters the queue. The team replies without leaving the workspace.
- GreetingFrequent questions get a draft. Sending follows the rule you define.
- AgentA complex request is handed to a person. The record stays when ownership changes.
Bulk SMS
A text campaign is prepared beside the conversation operation. Sending depends on consent and the carrier terms.
- CampaignThe message is written on this screen. The same team sees the inbox and the campaign together.
- AudienceRecipients come from your customer list. A tag decides who is included.
- RuleA number without consent is not included. Carrier and content terms still apply.
WhatsApp Business
The line, the template, and the campaign run from the channels screen. Sending depends on consent, template eligibility, and the platform rule.
- LineThe Business line lives on the channels screen. Active or paused shows on the card.
- TemplateA campaign is prepared with an eligible template. An unapproved template does not go out.
- RuleA person without consent is not included. The platform’s own limit and terms still apply.
AI
The draft is ready. The decision stays with you.
Frequent questions get a suggested reply. Complex requests go to an agent. What reaches the customer follows your rule.
- DraftAutomatic sending runs only in the case you define.
- HandoffBookings, orders, and complaints go to the right team.
- RecordTag and history stay on the same customer card.
Industries
One inbox. A different sale.
Hotels
Guest question
The booking draft stays in the same thread.
TravelTour request
A price question lands with sales.
CommerceOrder question
Shipping and product chats share the queue.
Real estateListing request
A viewing becomes an appointment.
Contact centerTeam in view
Channel and agent stay on one panel.
CorporateAppointment record
The request stays on the CRM card.
Questions
Before you decide.
Is Exemeta a chatbot?
No. Inbox, AI, social, WhatsApp, CRM, and voice sit in one operation. A chat assistant can be one part of that, not the whole product.
Does AI message customers on its own?
Under your rules it drafts, replies in defined cases, or hands the thread to a person. Complex requests stay with the team.
Which channels share one screen?
WhatsApp, Instagram, Facebook, Telegram, web live chat, and phone. What is live depends on the accounts you connect.
Do campaigns reach everyone?
No. Sending is limited by consent, contact preference, template eligibility, and the channel’s own rules.
How are data and privacy handled?
Access, retention, and a KVKK/GDPR approach are defined with your policy. This site does not claim a certification or a hosting country.
Company
You can see who you are talking to.
Exemeta is a Comnex Technology product. Demo, phone, and WhatsApp use the same line. Scope is set with your channels and your team.
- Productwww.comnex.ai
- Emailinfo@exemeta.com
- Phone0242 255 07 62
- WhatsApp0242 255 07 62
- AddressIFZA Business Park, Building A1, Dubai Digital Park, Dubai Silicon Oasis, Dubai, UAE