Questions about video testimonials

Zaply.me turns customers into a source of ad creatives. After a purchase or visit they record a video testimonial on their phone, receive a code for the submitted video and consent, and you get an edited file for Reels, TikTok, Meta Ads, and your page.

You send a private recording link — automatically after an order, or yourself. The customer accepts the terms, chooses how the video may be used, records about 20 seconds, and submits it. We trim pauses, add captions and your logo, then the files wait in your dashboard until you approve them.

No. The recording page opens in the phone browser. The customer can record with the camera or upload an existing MP4 or MOV file (up to 100 MB). There is no Zaply app and no extra login.

The file is uploaded and processed automatically. You get the original plus versions prepared for mobile, YouTube, and Instagram. The recording stays private until you approve it. Depending on your settings, the discount code is emailed immediately or after that approval. This means technical approval (the recording is clear and follows the rules), rather than an assessment of the review’s content. The code is for the submitted video and consent, on the shop's terms.

Yes. Every video waits in the dashboard. You keep what you want to use in ads, Reels, or on the site, and leave the rest private. Nothing is published without your action.

You keep the original recording and get processed versions prepared for mobile, YouTube, and Instagram. We remove pauses, add captions, and apply your logo so the files are ready to download and publish.

Connect WooCommerce. After an order is completed, Zaply can send the customer a recording invite while the experience is still fresh. You set your public slug, branding, and discount code in the dashboard.

Yes. You can share the recording link yourself — by email, SMS, or after a visit. That is how local services, beauty, gastronomy, and in-person businesses use Zaply without a store integration.

You choose the moment in shop settings. Immediate: the code is emailed after the video is submitted. Upon approval: the code goes out only once you accept the recording in the dashboard. You also set the code itself, for example WELCOME10. This means technical approval (the recording is clear and follows the rules), rather than an assessment of the review’s content. The code is for the submitted video and consent, on the shop's terms.

The code is a reason to record and a reason to come back. You get reusable sales videos and a repeat-purchase trigger. Used this way, the discount is an investment in content, retention, and customer value — not a one-off giveaway.

The recordings are collected for your shop, under the consents the customer gave. Your customer list stays yours — Zaply does not sell it. You decide what is stored, approved, downloaded, or deleted in the dashboard.

No. Create a free account, set your branding and reward, and send the first recording link. Shop plugins and apps are available when you want the invite to go out after an order. No credit card is required to try it.

Because the request arrives after a purchase or visit, the recording is short, and the discount is a concrete benefit. It is a clear exchange: about 20 seconds of video for a code they can use on the next order or visit.

A typical clip is about 20 seconds (minimum 15, maximum 60). The customer needs a phone with a camera or an existing MP4/MOV file, and must accept the terms before recording. We show three simple prompts, so they do not have to invent a script.

That recording stays in your dashboard. You approve only what you want to use. A black screen, a joke, or a poor take never goes to ads, Reels, or the site unless you decide otherwise.

Yes. Before the camera starts, the customer accepts Zaply's terms, the shop terms, and chooses how the video may be used: in ads and on social media, or on social media and shop website. Consent is part of the recording flow, not a separate follow-up.

They can choose social media and shop website, instead of ads and social. You should respect that choice when you publish. If they do not accept the terms, they cannot send the recording — and they do not receive a code.

Finishing is simpler when the link arrives after a purchase or visit and the reward is obvious. There is no app to install. There is a guided clip and a discount. You can also issue the code only after approval. This means technical approval (the recording is clear and follows the rules), rather than an assessment of the review’s content. The code is for the submitted video and consent, on the shop's terms.

No. The invite goes to a customer after a purchase or visit, whatever they say. The code is for the submitted video and consent, on the shop's terms. The shop decides which recording to show and must not present that selection as the full set of reviews.

No. The fee is for the number of generations in the plan, not for the next calendar month. The Free plan includes 3 generations. Paid plans offer 20 generations (Basic) or 50 (Professional) and are currently available only for accounts billed in Poland.

Unused generations from a paid plan stay on the account for 6 months from payment. After that they expire. The free plan does not use this 6-month window. Time passing on its own does not start a payment.

Only after you have used every generation in the paid pack. For a payment from Poland, a saved card can be charged automatically at that moment, unless you turn automatic payment off in the dashboard. Outside Poland a paid plan is unavailable for now.

You can still collect recordings, but editing stays paused until you pay for the next pack. After payment you start processing the videos you choose, manually, in the dashboard.

Caption correction is available in the Zaply dashboard for every store. It fixes speech recognition errors while preserving audio and editing. The video is reprocessed only after you save the draft and select “Render saved captions”. Saving a draft alone does not start rendering. The previous video remains available until rendering finishes. Rendering requires a supported video with its original file, reliable word timings, and an edit manifest. An editable draft alone does not mean an export can be rendered.

If the option is available for your video, open “Correct transcript”, select “Listen to segment”, and correct the spelling of the word you hear, for example “luna” to “Luna”. Select “Save draft”, then “Render saved captions” when available. Once the corrected video is ready, select “View corrected video” and download the export. Saving a draft alone does not change the MP4.

Correction fixes speech recognition errors while preserving audio, cuts, sequence, logo, framing, and the existing edit format. It is not for changing meaning, adding statements, cloning voices, or translating. The store must compare captions with the audio and review the finished formats before publishing within the customer’s consent.

Saving a draft and rendering a correction use no package generations and incur no additional charges. Rendering has a per-store limit over a rolling 24 hours, defaulting to 5 new requests; configuration may change this limit. Automatic retries of the same render create no new request or charge. Try later if the limit is reached.

A corrected export requires a ready video with its original file, reliable word timings, and a saved edit manifest compatible with the renderer. Older videos without a manifest may support saving a text draft if word data is available, but cannot render corrections while preserving the edit. Without reliable timings, segment editing is unavailable. Old edits are not automatically reconstructed.

The system records text versions, the author, and the time while preserving the base transcript. History and restoration are supported by the authenticated API; the current dashboard editor has no history or restore buttons. Restoration creates a new version and does not itself change the MP4 — a separate render is required. One-click restoration in the dashboard is not offered.

Copy your correction before selecting “Load current version” after a conflict. A failed render leaves the previous ready video available. Each field accepts one word of up to 160 characters without spaces; the preview is approximate. A long-text warning means you should review the export, not that readability is guaranteed.

Corrections belong to the video and require a session and store ownership checks; a recording link does not grant editor access. Text history and correction files are deleted with the video or account under service retention rules. Discarding unsaved text does not delete saved versions. Disabling rendering preserves history and ready files.

Once the feature is released, open Profile → Integrations → Integration rehearsal. The signed-in owner selects an actively connected store, checks its configuration and accepts the limits. The invitation preview sends no email. Record yourself, save the recording, start the test render and refresh the report. Finally, preview approval and the test coupon. Do not use customer data or recordings.

There is no charge and no production generations are used. Each company has 5 lifetime sessions shared across its stores, without renewal. A session lasts 24 hours and permits at most 2 render executions: the first attempt and one manual retry after failure. Deleting or expiring a session does not restore the allowance. WebM recording: up to 60 seconds and 50 MiB. This is not unlimited free rendering.

It checks private storage of the owner’s recording and a vertical 720×1280 edit. It excludes AI analysis, transcription, captions and production branding. Approval and rewards are simulated: the TEST-… code cannot be redeemed. No customer emails, real coupons, publication or verified-buyer badge. The rehearsal does not verify email delivery or real rewards. Run the separate WooCommerce connection test under WooCommerce → Zaply.me → Check connection.

Allow camera access in a browser supporting WebM. Retry a failed upload with the same recording; do not replace a successfully saved file. Refresh the report when the result preview expires — its link lasts at most 60 seconds. Do not create more sessions just because rendering is pending. A failed render allows one manual retry. After 24 hours the session expires; a new one requires remaining allowance. If access is denied, sign in as the current owner and check the store connection. Do not share the private session address.

In the report choose “Delete test recording and result”. If rendering is active or storage fails, retry deletion after work finishes. The owner can delete even after expiry or store disconnection. Access expires after 24 hours; automatic storage deletion is asynchronous rather than exactly at expiry. The allowance record remains. Accepting the rehearsal policy grants no advertising consent or licence.