Tally.so integration for repair shops

Copy your unique webhook URL from BytePhase and paste it into your Tally.so form’s webhook settings. Then submit one test response — BytePhase detects your fields automatically, you map them, choose whether submissions become leads or self check-ins, and press Activate.

No, and this catches people out. Tally.so is an online form builder. TallyPrime is Indian accounting software — a different product from a different company. The BytePhase integration on this page is Tally.so, the form builder.

You can connect it on every BytePhase plan, and the integration itself costs nothing extra. Each submission becomes a lead or a self check-in, and both of those are part of the Standard and Enterprise plans (and the 15-day free trial), so you need one of those to work with what comes in. Compare plans on the pricing page.

No. The connection is a direct webhook from Tally.so to BytePhase — no middleware, no code. Setup is copying one URL and clicking through a guided mapping screen.

Your choice per form: a lead — an enquiry with contact and device details ready to follow up — or a self check-in, a device intake that Reception converts into a full job in one click.

The webhook URL carries a key that is shown once and stored only as a hash, and you can set a signing secret so Tally.so signs every delivery and BytePhase verifies the signature before accepting it. Every request is rate-limited and scoped to your shop alone, and rotating the key instantly retires the old URL.

No. Tally.so sends a submission id with every delivery and BytePhase keys on it, so a retried or re-sent response updates the same record instead of creating a second one. Genuinely new submissions from the same customer follow the duplicate policy you set.

BytePhase matches Tally.so answers by the question’s label, so a renamed question arrives under its new name and its answer no longer lands in the BytePhase field you picked. After renaming, submit the form once and map the question again. If it was the name, email or mobile number question, check the Activity screen for failed submissions and retry them.

BytePhase turns Tally.so’s option IDs back into the text your customer chose, so a dropdown arrives as its wording and several ticked checkboxes arrive as one comma-separated value. File uploads arrive as links. Empty answers are left out. You then map each question to a BytePhase field in the Match fields step.

Open your form on tally.so and submit it once. The questions are captured in the BytePhase setup wizard for mapping. Until you press Activate, submissions are only logged as Received and nothing is created. After activating, you can retry that parked test from the Activity screen, or use Send test there to confirm a record is created.

Yes. BytePhase tells forms apart by Tally.so’s form ID, so one Tally.so integration can carry several forms, each mapped on its own. A repair booking form can create self check-ins while a quote request form creates leads. Each form also has its own rule for when the customer already exists. Use Add another form to connect the next one.