Widget Builder
What is Widget Builder?
Widget Builder lets you create custom workflow steps and data collection forms that guide users through specific processes within TMS.ai. Widgets appear as sequential steps when completing tasks like carrier onboarding, order processing, or compliance checks. Think of widgets as building blocks you assemble to create the exact workflow your operation needs. Each widget can collect specific information, display instructions, require document uploads, or trigger automations—and you control the sequence, requirements, and visibility for each step.
This matters because not every operation follows the same process. Your carrier onboarding might require specific insurance documents, safety certifications, and equipment lists that another company doesn't need. Widget Builder eliminates the one-size-fits-all approach, letting you design workflows that match your compliance requirements, operational standards, and business logic. Users follow your custom process step-by-step, ensuring nothing gets missed and everything happens in the right order.
How Widget Builder works:
- Access Widget Builder: Navigate to Settings, then to the module where you want to create custom widgets (typically found under Partners for carrier onboarding or similar workflow-driven processes).
- Choose the workflow to customize: Select the specific process you're customizing. For example, if building a carrier onboarding workflow, go to Widgets → Partner to create widgets for your partner onboarding sequence.
- Create a new widget: Click "Create Widget" and choose the widget type based on what you need to collect or display. Options include data entry forms, document upload steps, instruction panels, or confirmation screens.
- Configure widget details: Fill in the specifics for your widget. Give it a clear name like "Insurance Verification" or "Equipment Registration." Add instructions that explain what the user needs to provide. Set which fields are required versus optional.
- Add widget to workflow sequence: Once created, add your widget to the workflow by selecting it from available widgets and positioning it in the sequence. The order matters—users complete widgets from top to bottom, so structure the flow logically.
- Set the Submit widget last: Always ensure the Submit widget appears as the final step in your sequence. This is the confirmation button that completes the workflow, so it must come after all information-gathering widgets.
- Configure security settings for external users: If external parties (like carriers) will use this workflow, update security settings to control which widgets they can see. Go to the External tab, review the sequence, and toggle on widgets you want external users to access.
- Set up notifications: Configure notifications to alert your team when external users complete workflows. Choose whether to receive updates via email, in-app notifications, or both. This ensures timely follow-up on submissions.
What it means for you:
Widget Builder ensures critical workflows happen consistently and completely. When a new carrier begins onboarding, they follow your exact process: first uploading insurance documents, then providing equipment details, then completing safety certifications—whatever sequence your compliance requires. They can't skip steps or submit incomplete information because your workflow design prevents it. This eliminates the back-and-forth of requesting missing documents or clarifying requirements after the fact.
For your internal team, custom workflows create operational efficiency. Instead of manually checking whether each carrier provided all required information, the system guides them through your requirements and only allows submission when everything is complete. Your team receives notifications when workflows are done, with all collected information organized exactly where you need it. And because you control the workflow design, you can update requirements, add new steps, or modify processes without IT involvement—your operational standards evolve as fast as your business demands.