How to Write a Crowdfunding FAQ for a Phone-Paired LoRa Mesh Device
Prepared by the ChatField Editorial Team. Evidence reviewed August 18, 2026.
A crowdfunding FAQ is where cautious backers look after the headline video. Good answers reduce uncertainty. Weak answers repeat slogans, omit conditions or mix current J25 evidence with future-product plans.
Short answer
Write one answer per buyer decision. Start with the direct answer, name the exact model, describe the evidence conditions, state the limitation and link to the controlled document. Update the answer when the product or schedule changes instead of quietly editing the claim.
1. What is the product?
Describe it in one operational sentence. For current J25 use: the smartphone is the interface, Bluetooth connects it to the carried J25 terminal, and the configured terminal carries supported traffic through the local LoRa mesh to another equipped terminal and paired phone.
The terminal is not held like a conventional walkie-talkie. The phone alone does not transmit LoRa.
Link the How It Works page.
2. Does it need cell service, Wi-Fi or a gateway?
Explain which supported functions use the local J25 path and which activities may still require internet before or after field use. Do not confuse a local LoRa mesh with LoRaWAN gateway infrastructure.
3. How far does it communicate?
For current J25 evidence, state 5 km in urban-obstructed testing and up to 10 km in ideal open terrain. Explain that neither is a universal guarantee and that buyers should test their route.
For current planning, evaluate no more than two participating relay nodes where the tested layout and configuration permit. Do not multiply range by hop count.
4. Which phones are supported?
List verified phone platforms and versions or provide a compatibility test route. State required permissions and whether BYOD or company-managed phones have different support boundaries.
Do not answer “all phones” unless that statement is verified.
5. What can users send?
Name the supported PTT, text, image and location workflows for the exact model and application build. Separate intended, prototype and current functions.
6. What does the FCC evidence prove?
Current public J25 evidence includes FCC ID 2BVP9-J25. The record identifies authorized J25 equipment and applicable reports. It does not certify range, application quality, emergency use, J28 or every country.
Link the compliance page and J25 specifications.
7. Is the campaign showing a working prototype?
Label every visual as working prototype, appearance prototype, production-intent sample, production unit, diagram or concept. State hardware, firmware, application and date.
Kickstarter requires hardware creators to show working prototypes and does not allow photorealistic renderings in these categories.
8. What remains before production?
List engineering, tooling, testing, compliance, application, packaging, manufacturing, logistics and support milestones. Separate current completion from planned work.
9. How will lithium-battery shipping be handled?
Name the exact battery configuration and approved transport documents where available. State who handles export, freight, import and final delivery. Do not promise a universal shipping date before those stages are defined.
10. What support and warranty are included?
Publish only confirmed terms. State support channel, application and firmware responsibility, repair or replacement route and exclusions. Label anything awaiting confirmation.
11. Can business buyers request OEM or larger orders?
Separate consumer rewards from B2B production. ChatField's current B2B discussion begins at a minimum order quantity of 100 units. Branding, packaging, custom application functions and system engineering require separate scope.
Link the OEM and ODM page.
12. How should buyers contact ChatField?
Provide ChatField procurement support and vincent@chat-field.com. Ask for destination country, phone models, team roles, route, quantity and required workflows.
FAQ answer formula
- Direct answer: one sentence.
- Model: J25, J28 or exact future product.
- Evidence: test, specification, grant or prototype.
- Conditions: route, phone, version, market or configuration.
- Boundary: what the answer does not prove.
- Next step: document, test or contact link.
Claim review before publication
The FTC advises that advertising claims must be truthful, non-deceptive and supported before publication. Review implied claims created by images, headings and omissions—not only the literal FAQ text.
Sources reviewed
Kickstarter and the FTC do not endorse ChatField, J25 or J28. Their materials provide platform and advertising context, not approval of campaign claims.