PakshiTalk to us

Connecting your tools

What we build plugs into the tools your team already opens every morning. Nobody learns a new system, and nothing is typed twice.

Works with what you already use

We do not ask you to replace anything. Your team keeps WhatsApp, Tally, the spreadsheets and the billing software. What we build sits between those tools and moves the work along: an order read here, a voucher posted there, a payment link sent, a reminder on the right day.

These are the tools we connect to most often. If yours is not on the list, ask. Most business software built in the last ten years can be connected. We check in the first week of a Sprint and tell you plainly if it cannot.

WhatsApp Business
Orders, questions and follow-ups where your customers already are.
Tally
Vouchers, ledgers and stock, entered once and kept matching everywhere.
Zoho
Zoho Books, Zoho CRM (your customer list) and Zoho Inventory: read from and written to, without retyping.
Google Workspace
Gmail, Sheets, Drive and Calendar as the place your reports and reminders land.
Microsoft 365
Outlook, Excel and Teams for teams that live in Microsoft.
Razorpay
Payment links, receipts and reconciliation against invoices.
Shopify
Orders and stock from your online store into your books.
Telegram
Internal alerts and approvals for teams that prefer it.
Email
Plain email, read and sorted so nothing important waits.

Payments on UPI

Most customers now pay by UPI, and most businesses then spend an hour a day matching those payments to invoices. A payment arrives with a name that is not quite the customer's name and an amount that is not quite the invoice total, and someone works it out by hand.

We automate both ends. When a GST-ready invoice is raised, the system sends a payment link on WhatsApp for the exact amount. When the payment lands, the system matches it to the invoice and enters the receipt in your books. It flags part payments and short payments for a person, with the difference already worked out.

  1. Invoice raised

    The invoice is created once, in your billing software or in Tally.

  2. Link sent

    A payment link for the exact amount goes to the customer on WhatsApp, with the invoice attached.

  3. Customer pays

    By UPI, card or net banking. The link works with any UPI app.

  4. Payment matched

    The receipt is matched to the invoice by amount and reference, not by guesswork.

  5. Books updated

    The receipt voucher is posted to Tally or Zoho Books, and the customer's outstanding balance updates the same minute.

Invoices that are GST-ready

A GST invoice has to carry the right details every time. The customer's GSTIN and state. The HSN or SAC code for each line. The right split between CGST and SGST, or a single IGST line. An invoice number that never skips. Doing this by hand is where most errors come from. Doing it twice, once in the billing software and once in Tally, is where the rest come from.

We automate it as one set of steps. The system creates the invoice once, from the order or the quotation. It applies the tax lines from rules we set up with your accountant: which rate applies to which item, and when a sale is within your state or outside it. It sends the invoice to the customer on WhatsApp as a PDF, and enters the same invoice in Tally in the same minute, with nothing retyped. The UPI payment link goes out with it.

Created once
From the order or the quotation. Items, quantities and the customer's details are already there, so nothing is typed again.
Tax lines from your rules
Rates by item, CGST and SGST for sales within your state, IGST for sales outside it. Set up once with your accountant and applied every time.
Sent and entered
A PDF on WhatsApp for the customer, a voucher in Tally for your accounts, and a copy filed for the month's return.

India's data protection law

If you store customers' phone numbers, names or addresses, India's Digital Personal Data Protection Act, 2023 applies to you. It is written for everyone who keeps personal data, from a large bank to a two-branch pharmacy. The Act was passed in 2023, and its detailed rules are being brought in over time. The sensible thing is to build the habits now rather than in a rush later.

In plain terms, it asks four things of a business:

  • Consent and notice: tell people what you collect and why, and get their agreement. A customer who gives a number to place an order has agreed to that use, not to a marketing list.
  • Purpose: use the data for the purpose you gave and no other. Sending festival offers to a number collected for delivery updates needs a separate yes.
  • Deletion on request: when a customer asks you to remove their details, you must be able to find every copy and remove it. You keep only what the law makes you keep, such as invoices.
  • A named contact: publish the name of a person people can write to with questions or complaints about their data, and answer them.

Everything we build is set up with this in mind. Phone numbers sit in one place, not in five spreadsheets, so deletion is one action. The system records consent next to the number, with the date and what it was for. Marketing messages go only to people who said yes. The assistant never asks for more than the task needs. Who can open what is covered under who can access what on Keeping it safe.

One order, everywhere

One order, entered once

Here is what happens when a customer sends an order on WhatsApp, and every place it reaches without anyone typing it again.

Scroll sideways to see the whole route. The list below says the same thing in words.

One order on WhatsApp, entered everywhereThe order is read, posted to Tally, a payment link is sent, the payment is matched, a delivery note is printed for the godown, and the customer is told.when the payment landsAn order arrives onWhatsAppItems and quantitiesare readprices from your listSales order posted toTallystock checkedPayment link sent tothe customerRazorpay, on WhatsAppPayment matched to theinvoicereceipt postedDelivery note printedfor the godownCustomer told it hasshippedinvoice PDF attached

In words

  1. A customer sends an order on WhatsApp: in words, as a photo of a list, or as a voice note.
  2. The system reads the items and quantities and prices them from your own price list. It sends anything unclear back to the customer as a question.
  3. It posts a sales order to Tally and checks the stock.
  4. It sends the customer a payment link for the exact amount on WhatsApp.
  5. When the payment lands, it matches the payment to the invoice and posts the receipt.
  6. It prints a delivery note for the godown.
  7. It tells the customer the order has shipped, with the invoice attached.
For your technical teamInterfaces, tokens, logging

Connections use each product's official interface:

  • WhatsApp: the WhatsApp Business Platform, with approved message templates.
  • Tally: its XML interface over the local HTTP port, or scheduled exports where the machine is offline.
  • Zoho: the REST APIs, with OAuth.
  • Google Workspace and Microsoft 365: the Workspace and Microsoft Graph APIs for mail, sheets and calendars.
  • Razorpay: payment links and webhooks.
  • Shopify: the Admin API.
  • Telegram: the Bot API.
  • Email: IMAP and SMTP.

Every connection runs under a token scoped to the least access it needs. Tokens are stored outside the code and rotated at handover.

Every write to a system of record is logged: what was sent, when, and which rule or person approved it. That covers vouchers, receipts and messages to customers.

Tell us which tools you use

Name the software your team opens every day and the task that moves between them. We reply within one working day with whether it can be connected, and how.

Talk to us

hello@pakshitechnologies.com

Monday to Saturday, 9:30 am to 6:30 pm IST