ICON EV’s service team and warehouse team handled different parts of the same request. Service staff worked with dealers and tickets remotely; warehouse staff needed clear instructions for picking and shipping the required parts.

ICON trusted Fly More Kites to help connect that handoff.

The work linked HubSpot ticket data with document generation and warehouse printing, giving service staff a way to initiate the paperwork from the system they were already using.

Start with the information the warehouse needs

A useful pick slip depends on a complete request. The ticket needed the relevant shipping details, parts, and customer or dealer information.

The HubSpot forms and workflows provided a structure for that data. We used it as the foundation for the fulfillment documents rather than asking the service team to recreate the information in another message or file.

Generate a consistent document

We developed branded PDF templates for warranty and parts-purchase requests, connected to a document-generation tool.

A staff action in HubSpot triggered document creation. The resulting PDF was attached to the ticket, keeping the service record connected with the document sent into the fulfillment process.

The templates gave the warehouse a consistent presentation of the request and its required information.

Carry the handoff to the printer

The printing workflow used a designated Google Drive folder and folder-monitoring print software on a warehouse-connected computer.

When the generated document reached that folder, the print workflow sent it to the warehouse printer. Service staff could initiate the process remotely, while the warehouse received the physical slip needed for its work.

The people remained part of the process. Service staff completed and approved the request and triggered the action. Warehouse staff picked, packed, and shipped the parts.

Connect the systems with the physical task

The delivered work combined structured ticket data, document templates, PDF generation, ticket attachments, and the printing handoff.

Its purpose was straightforward: move the information from the service request to the place where the next team could use it.

ICON supplied the operational context and the need for that connection. We appreciate the opportunity to work on a practical detail that sits between software and the warehouse floor.

Automation projects do not always need a dramatic interface. Sometimes the useful outcome is a document arriving where the work happens, through a process people understand.

Have a handoff that still depends on copying information between tools and teams? Let’s see how the pieces could connect.

Put HubSpot to Work