Event
The save is the send
Marking an order ready, posting an instalment or saving an invoice sends the message. No second action for staff to forget.
Feature Detail Every message a jeweler sends,sent from the record it belongs to
SIYOQ is not a blank message box with a contact list attached. Templates are tied to modules, sends are tied to events, replies come back to the customer ledger, and consent is a field rather than an assumption. Here is all of it.
SIYOQ feature detail
Template library
Pre-drafted for the events a jeweler actually reports on
Each template is submitted for approval once, then filled from the JOS record — tag number, purity, net weight, instalment count, balance. No retyping from a bill.
ModuleSends onWhat the customer sees
Orders
Sends onBooked, in production, ready, delivered
What the customer seesOrder number, item and weight, expected date, collecting branch.
Repair and service
Sends onReceived, estimate ready, completed, collected
What the customer seesJob number, work done, charges, collection reminder.
Billing
Sends onInvoice saved, advance collected, payment received
What the customer seesInvoice number and amount with the tax invoice attached as a PDF.
Schemes and EMA
Sends onJoining, instalment due, instalment received, maturity, closing
What the customer seesScheme name, instalment number, amount and due date, maturity value on closing.
Outstanding
Sends onBalance due, ageing reminder, cheque due
What the customer seesOutstanding amount, ageing bucket, how to pay.
Approval and issue
Sends onIssued on approval, return due, return received
What the customer seesItem list with weights and the return due date — for wholesale counterparties.
Jobwork
Sends onIssued to karigar, received back, wastage settled
What the customer seesIssue number, metal weight, tunch and wastage on settlement.
Rates and offers
Sends onDaily publish, festival or scheme offer
What the customer seesRates by purity, or the offer. Promotional category, opted-in customers only.
Occasions
Sends onBirthday, anniversary, dormant, post-visit
What the customer seesA greeting or follow-up from the customer record, without pricing unless opted in.
Your own templates too.
Add any template in any category and map it to a JOS event. Drafting, submission and getting it through approval are part of onboarding, not a support ticket you raise later.
Triggers and sending
Automatic, scheduled, or by hand — set per template
Every template carries its own trigger rule, so the same library serves silent automation and counter-side manual sends without staff choosing between them.
Schedule
Date-driven reminders
Instalment due dates, approval return dates, cheque dates and ageing buckets generate reminders on a calendar.
Manual
Send from the screen
Staff send an approved template from the customer, order or invoice record when someone asks for a copy at the counter.
Review
Approval queue
Any template can be held for a manager to release, so nothing promotional goes out unchecked.
Media
Documents and images
Invoice PDF, estimate, repair photo, scheme passbook or catalogue image where the template permits it.
Guards
Duplicates and quiet hours
Repeat sends for the same event are blocked, and reminders can be held to working hours.
Two-way inbox
Replies are the point, so they land on the ledger
A customer who answers “coming this evening” is telling you something your system should know. In SIYOQ it does — beside the orders, schemes and balance that message belongs to.
Shared queue
Incoming messages sit in a queue visible to permitted staff, with the customer’s orders and balance beside the thread.
Assignment
A conversation is assigned to a salesperson, branch or department, so two people do not answer the same customer differently.
Customer context
Past purchases, running schemes, open orders and outstanding balance on the same screen as the message.
Service window
Within 24 hours of a customer message staff reply freely. Outside it only approved templates send — SIYOQ shows which state the thread is in.
Quick replies
Saved answers for making charges, exchange terms, hallmarking and timings, so every counter says the same thing.
Thread history
The full conversation stays on the record, so the next staff member sees what was already promised.
Consent and standing
Protecting the one asset you cannot replace
Your business number carries your reputation. Reports and blocks drop its quality rating, and a dropped rating cuts your daily limit. Consent handling is what prevents that.
Consent capture
Opt-in recorded against the customer with source and date — counter register, KYC form, scheme joining, website or app.
Category-level consent
A customer can accept order and payment updates while declining offers. Promotional templates only reach customers opted in for promotional messages.
Opt-out handling
A stop request from any channel is recorded once and blocks that number across every module, branch and template.
Suppression list
Opt-outs, repeated hard failures and do-not-contact numbers are excluded from every send automatically.
Audit trail
Who sent what, to whom, from which template and on whose consent, for any date range.
We will not help you break this.
SIYOQ does not send to numbers without consent and does not bypass template approval. Any tool offering that is risking your number, not its own.
Delivery and reporting
Status where the message came from, totals for the owner
Per-message state on the record it was sent from, and volumes, delivery rate and conversation usage rolled up for whoever signs the Meta bill.
1
Status
Per-message state
Sent, delivered, read or failed against each customer, with the reason where Meta returns one.
2
Failures
Retry and correction
Failed sends listed by cause — wrong number, no WhatsApp account, template rejected — so numbers get fixed and resent.
3
Reports
Activity by any cut
Volumes by template, module, branch, staff and date range. Delivery rate and read rate per template.
4
Usage
Conversation usage
Conversation counts by category, so you can reconcile against what Meta bills you.
5
Templates
Template health
Approval status, quality rating and rejection reasons for every template in one list.
6
Number
Sender health
Quality rating and current messaging limit for each connected number.
Administration
Built for groups, because most of the trade is one
Multi-branch, multi-entity, multi-brand and multi-language is the normal case in Indian jewelry retail, not an enterprise upgrade.
Multiple sender numbers
A separate verified number per branch, brand or legal entity, each with its own templates and reports.
Role permissions
Who can send, who can only read threads, who edits templates, who sees reports — set per role.
Languages
Templates maintained in the languages your counter uses: English, Hindi, Telugu, Tamil, Malayalam, Kannada, Gujarati, Marathi and Bengali.
Number hygiene
Formatting, country code correction and duplicate detection across the customer master before the first send.
Verification handled
We take you through Meta business verification, display name approval and number registration as part of onboarding.
Migration
Existing customer numbers and consent records imported with the consent source preserved.
Integration
Inside JOS, or alongside whatever you already run
SIYOQ ships as part of the Jewelry Operating System, and works as a standalone service for businesses on other software.
With JOS
No integration work. Templates, triggers, inbox and reports appear inside the modules your staff already use.
With your system
A REST API to send a template with its variables, attach a document and read delivery status back into your own records.
Status callbacks
Delivery, read, failure and inbound reply events pushed to an endpoint you nominate.
Without a system
Customer master and consent flags by file upload, for businesses running on registers and spreadsheets today.
Onboarding contact
A named person through verification and go-live, then support on your normal SIONIQ channel.
Export and deletion
Message history and reports exportable at any time. Disconnect stops sending immediately; deletion on written request.
Limits worth knowing
What the platform will not do, stated before you buy
These are Meta’s rules, not ours. Every provider works inside them; some are less direct about it.
Channel availability
Onboarding a business onto the WhatsApp channel depends on Meta’s business verification, display name approval and template approval. SIONIQ’s platform access is subject to Meta’s own review process, and timelines are set by Meta.
Templates need approval
Meta reviews every template before use. Approval takes time, and promotional wording inside a utility template is the most common rejection.
Limits ramp up
A new number starts on a lower daily limit that grows with quality and volume history. Bulk sending on day one is not possible.
Conversation charges apply
Meta charges per conversation by category and country, billed on usage and separate from the SIYOQ fee. Rates are set by Meta and change.
You are the sender
Each business connects its own WhatsApp Business Account. We do not send from a shared number, so account standing stays with you.
Consent is mandatory
Messaging customers who have not opted in leads to blocks and a lower quality rating. SIYOQ will not override this.
Not a broadcast blaster
If the plan is untargeted promotional volume to purchased lists, SIYOQ is the wrong product and Meta will shut the number down.
Get Started
See it running on your own orders first
Send us your branch count and the modules you run. We will set up the templates, take you through verification and show the reports on a demo instance before anything is signed.