SK Digital is one workspace for running a small business. Customers reach you on WhatsApp, Instagram or your Google Business Profile, and you answer all three from one dashboard — alongside the CRM, product catalogue, quotations and invoices, staff tasks and automations that follow from a conversation. WhatsApp shares the contact record with the CRM, so a lead answered there is the same customer you invoice; Instagram is answered in the same dashboard but is not yet written to that record. WhatsApp messaging runs on Meta's official WhatsApp Business Platform (Cloud API): you connect your own WhatsApp Business Account and keep ownership of it, and we handle the API infrastructure, authentication and delivery.

Click "Sign Up" in the top navigation and enter your mobile number. You will receive a one-time code to confirm it, and you are in — no WhatsApp Business Account is needed to create the account or look around. From the services hub you then connect whichever channels you want: WhatsApp through Meta's Embedded Signup (or your own access token), Instagram, and your Google Business Profile.

No. Meta's Embedded Signup will create or connect one for you inside the flow. If you already have a WhatsApp Business Account you can connect it that way too, or paste an access token from Meta Business Manager instead. You also do not need WhatsApp at all to use the CRM, store, Google Business Profile or the other services.

Any number that can receive a verification code by SMS or voice call — mobile, landline or VoIP. Which numbers are eligible depends on the path you take. Ordinary Cloud API onboarding needs a number that is not registered on the WhatsApp personal or Business app, and once it moves to the API it cannot also be used on the app. Coexistence is the exception: a number already running on the WhatsApp Business app can join the platform and keep working there, by scanning a QR code in the app rather than being moved. Do not remove a number from the Business app before checking whether coexistence covers it.

Starter is ₹999/month and covers the core workspace for small businesses, including WhatsApp, Instagram, Google Business Profile, Mini CRM, E-Store, Business Dialer, Video Studio, API access and 1,000 included platform messages. Growth is ₹2,999/month and adds Pro services such as Marketing & Publisher, Staff & Tasks, Payments & Documents and Institute Management, with 5,000 included platform messages.

You can create an account without a credit card, complete your business profile and explore the workspace before choosing a paid production plan. Some provider features require connecting your own Meta, Google or other provider account.

Embedded Signup is Meta's official flow for connecting a WhatsApp Business Account to a platform like SK Digital: you log in with Facebook, select or create a Business Manager, verify your business phone number, and authorize SK Digital to send messages on your behalf. It runs here in a Meta-hosted window, so no credentials are typed into our site. Connecting with an access token from Meta Business Manager remains available if your administrator prefers it.

Meta's business verification typically takes 1-3 business days. During this time, you can use your account in limited mode (up to 250 conversations per day). After verification, your messaging tier may increase based on quality ratings.

Meta limits how many unique contacts you can message per 24 hours based on your business quality and verification status. Tier 1: 1,000 contacts/day. Tier 2: 10,000 contacts/day. Tier 3: 100,000 contacts/day. Tier 4: Unlimited. Your tier increases automatically as you send more messages with high quality.

If your number was rejected, the most common reasons are: the number is already registered on WhatsApp (personal or Business app), the number is on a platform's blocklist, or there was a verification code delivery failure. Try using a different number or contact our support team at support@meta.sanjusk.in for help.

Yes, through coexistence. Scan a QR code in the WhatsApp Business app and the same number joins the platform while continuing to work on your phone, with recent chats imported into the shared inbox. Without coexistence a number can only be registered in one place — the personal app, the Business app, or the Business API — and moving it to the API means removing it from the app first.

Message templates are pre-approved message formats required for initiating conversations with customers (business-initiated messages). They must be approved by Meta before use. Templates can include text, media (images, videos, documents), and interactive buttons. Session messages (replies within 24 hours of customer contact) do not require templates.

Meta typically reviews template submissions within a few minutes to 24 hours. Complex templates or those in sensitive categories may take longer. You'll receive an email and in-dashboard notification when your template is approved or rejected.

Common rejection reasons include: content that violates WhatsApp Business Policy (gambling, adult content, alcohol promotions to minors), misleading content, poor grammar, templates that try to collect sensitive information, or templates that look like phishing. SK Digital provides rejection feedback to help you revise and resubmit.

Template variables are represented as {{1}}, {{2}}, etc. in the template body. When sending, you provide the corresponding values in order. For example, a template "Hello {{1}}, your order {{2}} has shipped" would receive values ["John", "#12345"] to produce "Hello John, your order #12345 has shipped."

WhatsApp has three template categories: UTILITY (transactional messages like order confirmations, shipping updates, appointment reminders — lowest cost), AUTHENTICATION (OTP messages), and MARKETING (promotional content, offers — higher cost per conversation). SK Digital displays the pricing difference when you create templates.

You cannot edit an approved template. You must create a new template with the desired changes and submit it for approval. The old template remains active until the new one is approved. We recommend creating new templates with version identifiers (e.g., order_confirmation_v2) to keep track of iterations.

SK Digital charges the platform subscription separately from Meta. WhatsApp messaging charges follow Meta's current pricing rules for the business and destination, and may change independently of the SK Digital plan. The dashboard should be treated as the workspace fee plus applicable provider usage.

SK Digital plan pricing is monthly: ₹999 for Starter or ₹2,999 for Growth. Connected providers such as Meta can have separate usage charges under their own current pricing, so provider usage is not represented as unlimited by the platform subscription.

We accept all major credit cards (Visa, Mastercard, American Express, Discover) and ACH bank transfers for annual plans. Enterprise customers can request invoice-based net-30 payment terms. We do not accept cryptocurrency payments.

You can cancel your subscription at any time from Account Settings → Subscription → Cancel Plan. Your access continues until the end of the current billing period. No refunds are provided for partial months. After cancellation, your data is retained for 30 days before deletion.

Starter includes 1,000 platform messages per month and Growth includes 5,000. These are SK Digital platform allowances and are separate from any Meta or other provider charges that may apply to the connected service.

Sign in and go to Developers → API keys → Create key. Give it a name so you can tell your integrations apart. The key is shown once, at that moment — copy it straight into wherever your code reads its secrets. If you lose it, revoke it and create another; revocation takes effect immediately.

It is available to every account with no extra step. A key acts as its owner, on the WhatsApp number that owner connected, and can never see or send from anyone else's — an account or phone number in a request body is never trusted to widen that.

https://meta.sanjusk.in/api/v1. Every request carries your API key as a bearer token: "Authorization: Bearer mbsp_your_key_here". Requests and responses are JSON. Start with GET /api/v1/status — it confirms the key works and names the number it sends from.

60 requests per minute per key for the sending endpoints, and 120 per minute for GET /api/v1/messages. Going over returns HTTP 429 with a Retry-After header giving the seconds to wait. The limit is counted per key rather than per account, so one runaway integration cannot exhaust another one's budget.

Two ways, delivering the same messages — pick whichever matches where your code runs. If your server has a public URL, add it under Developers → Webhook destinations and we POST each message to it as it arrives. If it does not — a desktop tool, a script behind NAT, a scheduled job — poll GET /api/v1/messages instead, passing the nextSince value from the previous response so you cannot miss a message or receive one twice.

Every delivery carries an HMAC-SHA256 of the raw request body in the X-Metabsp-Signature-256 header, computed with that destination's own secret. Compute the same HMAC over the raw body, compare in constant time, and only parse the JSON once it matches. Your URL is reachable by anyone who guesses it, so this check is what makes the request trustworthy. The Developers → API reference tab has working code.

That is keyword routing. Give each destination an entry keyword: a message starting with that keyword goes to that destination, and the rest of the conversation stays with it until the person goes quiet or sends STOP. A message matching no keyword goes to every destination that has no keyword of its own, plus any marked as a fan-out fallback. With a single destination and no keyword you simply receive everything.

The delivery is retried twice more, after 5 seconds and again after 15. If all three attempts fail, the destination is marked failing and the last error is shown against it in Developers → Webhook destinations. Answer within a few seconds and do your real work afterwards — a slow endpoint is treated the same as a broken one.

Not yet. The API is plain HTTPS with JSON, so any HTTP client works — the Developers → API reference tab has copy-paste curl for every endpoint, and the developer docs include a Node.js webhook handler you can lift directly.

First, check the message status in your dashboard — it will show queued, sent, delivered, or failed with an error code. Common issues: (1) Phone number not registered with WhatsApp. (2) Recipient has blocked your number. (3) Template not approved or content mismatch. (4) Your messaging tier limit reached. (5) Your phone number has been flagged for quality. Check our error code reference in the docs.

Error codes from Meta are documented at developers.facebook.com/docs/whatsapp/cloud-api/support/error-codes. Common codes: 130429 (rate limit hit), 131030 (recipient number not WhatsApp), 131047 (message expired), 131051 (unsupported message type). SK Digital also shows human-readable descriptions alongside error codes in the dashboard.

Troubleshooting steps: (1) Verify the webhook URL is publicly accessible (not localhost). (2) Confirm your server returns HTTP 200 within 10 seconds. (3) Check the webhook logs in SK Digital dashboard for delivery attempts. (4) Verify your server is validating the HMAC signature correctly (signature mismatch causes delivery to stop). (5) Check that your server is not blocking our IP ranges.

Meta monitors the quality of messages sent by each phone number based on user feedback (blocks, reports, opt-outs). A yellow or red quality rating means users are reporting your messages negatively. This can reduce your messaging tier. To improve: review your message content, ensure proper opt-in, honor opt-outs promptly, and reduce sending frequency.

You can migrate your existing WABA to SK Digital by connecting it with an access token, phone number ID and business account ID — migrating through Embedded Signup is coming soon. You will need access to the Facebook Business Manager that owns the WABA. Phone numbers, templates, and business profile settings will carry over. Message history is not migrated. Contact support@meta.sanjusk.in for migration assistance.