A practical path
from concept to Bitrix24.

What to demonstrate

1. Open the homepage and explore a service through the menu.
2. Choose an industry and follow its relevant services.
3. Open Request a Quote, enter sample details, and preview the request.
4. Use the top-right Customer Resources button. Choose Personal Credit, Business Credit, EFT, or Credit Card.
5. For a paper application, select Scan or Upload Completed Form in the Original Document panel. Try Sample Paper Form to show automatic extraction. Then show the customer reviewing and editing suggested answers beside the scan, selecting which answers to use, and confirming their accuracy. Unselected web-form values stay intact; the scan itself is not submitted.
6. Select Load Sample Details, then Fill & Review Application. Compare the filled PDF with the original blank form.
7. Download the filled application, then click Preview Department Routing to show the proposed handoff.
8. Resize to mobile to show the compact menu and stacked layouts.

Rebuild map

What needs account access

This is a Sites-hosted prototype, not an exported native Bitrix24 template. Its HTML and CSS are reusable references. Native blocks will need to be rebuilt or custom HTML blocks adapted after checking the account’s permissions and plan. Exact font availability, editable block options, portal links, and CRM workflows remain to be verified.

The demo quote form validates entries locally and shows a request summary. It sends no email, creates no CRM record, and stores no details. Customer login links to the existing portal; no portal development is included.

Applications that move work forward

Customer Resources combines account access, applications, and reference tools at /resources/, reached by a single button at the top right. The previous /forms/ hub redirects there; individual application addresses remain available. The fixed header keeps navigation visible on desktop and mobile, and section links jump to the portal, applications, reference tools, or FAQs. Each of the four public applications has a matching web form. The demonstration fills the original PDF in the browser, preserves its printed terms, and offers a document preview and download. Signatures remain blank; documents are labeled unsigned demonstration copies.

Department labels are a proposal, not verified recipients. The routing button demonstrates the handoff but sends no email and creates no CRM record. No application details are saved by this prototype. Sensitive identifiers and payment credentials use fixed demonstration placeholders; do not enter real information.

Paper applications and customer review

Customers can keep using paper applications. In this prototype, each Original Document panel offers a completed-form import using a PDF, scanned image, or phone photo. The browser reads the information page locally and suggests answers only for editable fields. The customer sees the source scan, corrects missed or misread text, checks marked choices, selects the answers to use, and explicitly confirms accuracy before anything fills the web application. Existing values remain unless the customer selects their replacement. Customers can edit the web form again and review the filled PDF before the proposed handoff.

The sample-paper option generates and reads an actual sample document; it does not load canned extraction results. Files and unused extraction results stay in browser memory and are discarded when the import window closes. Selected answers remain in the open web form until the customer leaves or edits them. Source signatures and locked sensitive fields are never imported. The demo accepts up to three pages and 15 MB of sample or redacted PDFs, JPGs, PNGs, or WebP images. Recognition depends on an upright, closely cropped copy of the matching original form; skewed photos may need retaking.

The local reader works best on printed entries. Handwritten answers may be missed or misread and require customer correction. Production should evaluate a handwriting-capable document-recognition service against actual Fronk forms, with protected uploads, verified field mapping, customer review, and an agreed retention policy. Preserve the original signed application as a protected source record; importing text does not replace signatures or supporting documents.

Production form workflow

1. Confirm the department, responsible employee, and inbox for every application. Approve the original terms, required fields, permissions, and document templates.
2. Create native Bitrix24 CRM forms or a secure embedded form. Add completed-paper import with handwriting-capable recognition and mandatory customer review. Map every input to a CRM field and assign the submission to the agreed team.
3. Collect required permits and EFT supporting documents through authenticated, access-controlled uploads. Add the approved signature and consent workflow before an authorization is considered complete.
4. Generate the completed application using Bitrix24 document templates where available, or a secure server integration that fills the original PDFs. Verify the account plan supports the chosen automation; the browser demo is a reference implementation.
5. Automatically deliver the completed document or a protected document link to the relevant department, with CRM status, timestamps, and a failure/retry path. Use the mailbox and automation configured in Fronk’s account.
6. Run an end-to-end test for each form: validation, field mapping, document generation, signature/attachments, department assignment, delivery, and receipt. Launch only after recipients and Fronk approve the results.

Card entry must use a hosted payment-provider form and tokenization. Do not collect or email full card numbers or security codes through ordinary CRM fields. Bank details and personal identifiers need restricted access, protected transmission, and an agreed retention policy. Email notifications can point to a protected record rather than expose sensitive data in an attachment.

The fuel-tax link on the current site opens a Bitrix24 sign-in page. No tax application was invented. The hub retains that link and verified Texas and Oklahoma tax resources, plus the Hall Tank calculator. Add any specific approved tax application once Fronk supplies it.

Scope for the proposal

Include the Customer Resources page, four web forms, completed-paper uploads and handwriting recognition with customer correction/confirmation, PDF field mapping, approved signature and attachment handling, department routing, secure payment integration, and end-to-end testing as explicit implementation scope. Confirm Bitrix24 plan costs and any payment, signature, or integration service fees before quoting the production workflow.

Brand and content continuity

The original Fronk Oil logo is retained. All photographic imagery is replaced with real Pexels stock photos. Current contact information, product availability, delivery area, and service descriptions should be confirmed before launch. No new testimonials or service guarantees have been added.

Stock photography credits

Original Pexels photographs depict industry applications; they do not depict Fronk Oil vehicles, facilities, or employees. All photographic imagery in this proposal uses real stock photos. No AI-generated media is included.

• Hero: Photo by Alexander
• Agriculture: Photo by Dariusz Grosa
• Fleets: Photo by Kelly
• Construction: Photo by Maarten van den Heuvel
• Industrial: Photo by Ali Mucci
• Repair: Photo by Artem Podrez

Pexels License · Download photo source records

Template package

The package includes the page markup, reference styling, demo interactions, and implementation guide. It is a starting point for adaptation, not a one-click Bitrix24 import.

Official implementation references

Bitrix24 CRM-form email automation
Bitrix24 CRM paperwork automation

Bitrix24 custom CSS documentation
Bitrix24 site and page settings