Turning Lead Chaos into Clarity: How a Massachusetts-Based Manufacturing Business Transformed Its Sales Reporting Summary Sales teams generate a steady stream of leads across sources like trade shows and referrals, yet most organizations can’t answer a simple question in real time: “How is our pipeline actually trending this month?” We built a single-page Sales Dashboard using Dynamics 365 Customer Service lead data and Power BI, giving revenue teams a live, filterable view of lead volume, process stage, qualification, and source mix, all driven by two global slicers: Account and Date Range. The result: manual weekly lead tracking was replaced with a live view that surfaces channel performance and process bottlenecks the moment they appear. Table of Contents 01 Summary 02 About the Customer 03 The Challenge 04 The Solution 05 Dashboard Overview 06 Lead & Stage Trends 07 Source & Geography 08 Business Impact 09 FAQs 10 Conclusion About the Customer Customer Spotlight A US-Based Manufacturing Business Rebuilding a Century-Old Category Headquartered in Massachusetts, our customer is a US-based manufacturer that set out to fix a problem no one had touched in over a century: cooking appliances still running on decades-old heating technology. After five years developing a proprietary heating alloy and real-time smart algorithms, the team launched the world’s first touchscreen toaster, which has since become a #1-selling smart toaster with national media recognition. As the company scaled, it needed a single, always-current view of sales pipeline health to match its fast-growing customer base. The Challenge Dynamics 365 Customer Service captures every lead reliably. The gap wasn’t data capture. It was turning that raw lead data into a view sales leadership could actually act on. Sales managers frequently found themselves asking: 1Is lead volume growing or flattening month over month? 2Where are leads getting stuck in the sales process? 3How many leads are actually converting to Qualified? 4Which lead source is driving the most volume? 5Can we filter all of this down to a single account instantly? Answering these meant exporting Dataverse views into spreadsheets and manually re-pivoting, a process that was slow, error-prone, and quickly out of date. The Solution To eliminate manual reporting, we designed a centralized Sales Dashboard in Power BI using Dynamics 365 Customer Service Leads as the data source. The report is built as a single interactive canvas covering: Lead Volume Trends Month-by-month tracking of lead creation to spot pipeline generation swings early. Business Process Stage Real-time view of how many leads sit at each stage of the sales process flow. Dynamics 365 Customer Service Integration Primary data source connecting lead records, source, county, and qualification status. Power BI Analytics Layer Global Account and Date slicers, source-mix pie charts, and geographic breakdowns. Dashboard Overview The dashboard gives sales leadership an instant read on pipeline health. It consolidates the key lead metrics into one interactive page: Count of Leads Leads by Month Business Process Stage Qualified Leads Qualified by Month Lead Source Mix Leads by County Account Filter Date Range Filter The dashboard includes interactive filters for Account and Date Range at the top of the page, enabling instant re-analysis across any account or time window without rebuilding a single visual. Lead & Stage Trends Rather than reviewing lead counts only at month-end, management can continuously monitor: Monthly lead creation volume vs. prior months How many leads currently sit in each business process stage Qualified lead volume by month, compared against total leads created These trends quickly surface slowing lead generation, stalled leads sitting too long in the pipeline, or a widening gap between leads created and leads qualified, turning lead tracking into an operational management tool rather than a monthly snapshot. Lead Source & Geographic Breakdown Understanding where leads come from matters as much as how many arrive. The report breaks leads down by Lead Source and County, helping marketing and sales identify: Which channel, trade show or referral, is driving the most volume Whether marketing spend is aligned with actual lead-generating channels Gaps in geographic data capture, such as an unpopulated County field Regional concentration of leads once location data is fully captured Filtering by Account and Date Using the page-level Account and Date slicers, users can instantly narrow the entire dashboard to answer strategic questions such as: How is a specific account’s lead activity trending? How did lead volume compare across a specific quarter? Where should the next trade-show investment go? Business Impact Before After Lead volume tracked manually in spreadsheets Live month-by-month lead trend in Power BI No visibility into where a lead sits in the sales process Business Process Stage visual shows real-time stage distribution Lead source ROI discussed anecdotally Lead Source pie chart quantifies channel contribution instantly Filtering by account meant exporting and re-pivoting data One dropdown filters the entire dashboard to a single account Qualified lead conversion checked only at month-end Continuous lead-to-qualified tracking across the year Frequently Asked Questions 1Does Dynamics 365 Customer Service provide pipeline reporting out of the box? Dynamics 365 Customer Service captures the underlying lead and process-flow data, but organizations typically need a customized Power BI report to combine lead volume, stage, source, and geography into one actionable view. 2Why show Business Process Stage alongside lead volume? Volume alone doesn’t tell you if leads are moving through the pipeline. Pairing stage distribution with monthly volume shows both how many leads are coming in and where they’re getting stuck. 3Who benefits most from this type of report? Sales leadership, marketing teams, and account managers all benefit. Leadership gets portfolio-level pipeline visibility, while account managers can filter straight down to a single account’s lead activity. 4Can this be extended to Opportunities? Yes. The same Account and Date slicer pattern can be reused on an Opportunity-based page to track pipeline value and win rate alongside lead volume. Conclusion Pipeline health is measured by more than how many leads come in. It’s defined by how well they move, where they come from, and whether the data behind them is trustworthy. By connecting Dynamics 365 Customer Service … Continue reading Turning Lead Chaos into Clarity: How a Massachusetts-Based Manufacturing Business Transformed Its Sales Reporting →

Insights & Field Notes Summary Account data in CRM is rarely in one place. Revenue, pipeline, quotes, and years of meeting notes live across many separate records. We built a one-click Account Intelligence Report that runs inside Dynamics 365 and assembles the full account picture on screen in seconds. A second click runs an AI analyst over every appointment note, producing a plain-language engagement history, current status, open commitments on both sides, and talking points for the next meeting. The complete report, facts plus AI insights, exports as a branded, editable Microsoft Word document with a single click. It runs entirely within the signed-in user’s own Dynamics session. No new servers, no third-party libraries, and it inherits the user’s existing data permissions by design. Table of Contents The 40-Minute Problem One Button, Total Account Intelligence What the Report Actually Contains The AI Analyst: Years of Notes in One Read From Screen to Boardroom: One-Click Word Export Under the Hood: How It Works (and Why It’s Safe) Business Impact FAQs 01The 40-Minute Problem Picture an account manager thirty minutes before a quarterly business review with a customer they have worked with for three years. The relationship is rich. The context, though, is buried. The revenue figure sits on the Account. The live pipeline is spread across a handful of opportunity records. There are a dozen quotes from the last two quarters, most of them not tracked and easy to forget. Then there are the meeting notes. Dozens of appointments, each with its own thread of what was said, promised, and agreed. None of that is missing. It is all in the CRM. The trouble is that it is everywhere at once. To reconstruct the story of an account, someone has to open twenty records, read between them, and hold the whole picture in their head. So they do not bother. They skim the last two meetings, walk in half prepared, and the deeper context stays invisible until it becomes a problem. This is not a data problem in the sense of not capturing enough. It is a synthesis problem. The organisation already holds the intelligence. It simply has no fast, trustworthy way to assemble it into something a human can act on before a meeting begins. The real bottleneck The hardest work in account management is rarely finding the information. It is pulling it together. Connecting revenue, pipeline, and history into one coherent, current view, at the exact moment you need it, is where most of the effort actually goes. 02One Button, Total Account Intelligence We set out to solve that synthesis problem with the smallest possible footprint, for a U.S.-based manufacturing facility running Dynamics 365 Sales. The result is a single command on the Account form called the Account Intelligence Report. From the account you are already looking at, one click opens a clean, paper-style report inside the application. It is not another tab to manage or another system to log into. It is part of the CRM you already use. The report does three things, in order: It gathers. In seconds it pulls the account’s revenue, its sales-revenue targets, the most relevant quotes, every open opportunity, and all related appointments together with their notes. It reads. A second click sends those meeting notes to an AI model that writes up the account’s engagement history and distils it into clear, decision-ready insights. It delivers. One more click produces a professional, branded Word document, a finished brief you can email, print, or bring into the meeting. The whole experience is built to feel instant. You stay in the flow of your work, and the report comes to you. 03What the Report Actually Contains The report is organised the way an account manager actually thinks about an account, not the way a database is organised. At the top is a compact dashboard. Revenue, quote totals, open opportunities, and appointment counts sit at a glance. Below that is the structured document itself. Revenue and pipeline at a glance The opening section brings together the numbers that frame the relationship: the customer’s revenue, the potential opportunity, budget and revenue year-to-date, and the estimated revenue outlook. This single block replaces what would otherwise mean cross-referencing the Account record with a separate sales-revenue table. Quotes and open opportunities Next is a focused view of quotes from the last six months, including those not tracked quotes that quietly accumulate and are easy to lose, alongside every open opportunity in the same window, with its stage, originating lead, product segment, and bid date. Totals calculate automatically, so pipeline value is always visible without a manual add-up. Every related appointment, with its notes This is where the report earns its keep. It lists all related appointments and, crucially, lets you expand any meeting to read exactly what was discussed. Attendees are pulled out, and the full substance of each meeting is available inline. For a customer with a long history, this becomes a navigable timeline of the entire relationship, every visit, call, and commitment, in one place. Why appointments are the hard part Meeting history is usually collected through two different paths in CRM. Sometimes a customer is recorded as a participant, sometimes as the subject of the meeting. The report queries both, then merges and de-duplicates the results, so nothing is missed and nothing is doubled. 04The AI Analyst: Years of Notes in One Read Gathering the notes is only half the battle. Someone still has to read them. The “Get AI Insights” action does exactly that. It takes the full set of appointment notes for the account and asks an AI model, Azure OpenAI, to do what a thorough colleague would do before a meeting: read everything, then tell you what matters. The output is deliberately structured, so it slots straight into the report rather than producing a vague paragraph. It returns six things: Engagement history — a single flowing narrative of the relationship from the earliest meeting to the most recent, with dates, attendees, and … Continue reading From CRM Silos to a Board-Ready Brief: An AI-Powered Account Intelligence Report Inside Dynamics 365 Sales →

Summary Automated end-to-end contract generation, digital signing, and document filing for an Australia-based commercial linen and garments company using Dynamics 365 Sales, Microsoft Power Automate, and Adobe Acrobat Sign. Eliminated manual contract preparation by generating personalized Word contracts directly from accepted Dynamics 365 Quotes using a reusable Word template. Leveraged Adobe Acrobat Sign text tags embedded within the Word template to automatically create signature, date, and fillable fields without manual field placement or custom development. Automated agreement creation, customer notifications, and real-time signing status tracking through Adobe Acrobat Sign, providing complete visibility throughout the contract lifecycle. Implemented a dedicated child Power Automate flow that automatically identified completed agreements from Adobe Sign emails and archived signed contracts into the correct SharePoint document library. Reduced contract turnaround from a manual, multi-step process to a one-click, fully automated workflow while ensuring audit-ready signed documents and eliminating manual document handling. Table of Contents Introduction Business Challenge Procedure End-to-End Flow Why This Approach Works Conclusion Introduction For any business that runs on contracts — service agreements, quotes-turned-orders, vendor sign-offs — the gap between "quote accepted" and "contract signed" is often where deals slow down. Manual document preparation, back-and-forth emails, chasing signatures, and manually filing signed copies all eat into time that should be spent serving the customer. For an Australia based Linen and Garments, a commercial textile services company, CloudFronts built an end-to-end automation that takes a sales quote all the way through to a fully signed, filed contract — with zero manual document handling in between. The solution combines a Word contract template, Microsoft Power Automate, and Adobe Acrobat Sign, orchestrated across two connected flows: a parent flow that creates and sends the contract, and a child flow that listens for the signed response and files it automatically. This post walks through how that solution works, including the one detail that makes the whole thing possible without any custom code: Adobe Sign text tags embedded directly inside the Word template. The Business Challenge Once a quote is accepted, the team needed the resulting contract to: Be generated automatically from the quote and its line items — no manual copy-pasting of customer details into a Word document. Be sent for signature immediately, with the right fields ready for the customer to fill in and sign — bank details, account information, and a signature block, all in the right place. Notify both the customer and the internal Adobe Sign account holder the moment it’s out for signing. Automatically file the final, fully signed PDF back into the correct SharePoint location tied to that quote — without anyone needing to remember to save it. Doing this by hand across multiple people and mailboxes was slow and error-prone. The goal was to make the entire journey — quote to signed, filed contract — happen in minutes, with no manual document work at any step. Procedure Step 1: Auto-Generating the Contract from the Quote The process starts with a single action: Create Contract. This triggers the parent Power Automate flow, which: Composes the Quote ID from the selected record. Retrieves the document location tied to that quote (the Word contract template). Pulls the Quote, the associated Customer, and the Contact record for the signer. Uses these to populate a Word template — the standard “Populate a Word Template” merge step — filling in customer name, contract terms, line items, and contact details automatically. This is the same idea used in most contract-automation flows: merge structured CRM/quote data into a pre-built Word template, so the resulting document is fully personalized without a single manual edit. Step 2: Making the Contract Signable — Text Tags in the Template This is the step that makes the entire signing experience work, and it's worth explaining properly, because it's easy to get wrong. A merged Word document, by itself, is just static text. For Adobe Acrobat Sign to know where a customer needs to sign, initial, or fill something in, the template needs special markers called text tags — plain text strings embedded directly into the Word template before it's ever merged. When the finished document is sent to Adobe Sign, Adobe automatically scans it, finds these tags, and converts them into live, interactive fields for the signer. For the contract, the template includes tags like: {{Customer_Sign_es_:signer1:signature}} {{Date_Of_Signature_es_:signer1:date}} {{Financial_Institution_es_:signer1}} {{BSB_Number_es_:signer1}} {{Account_Name_es_:signer1}} {{Account_Number_es_:signer1}} Each tag follows Adobe's syntax: a field name, the _es_ identifier, the signer role (signer1), and an optional field type (signature, date, or left blank for a plain fillable text box). Because these tags are just text, they can sit anywhere in the Word template exactly where the business wants the field to appear — no separate field-placement tool required. Getting this right matters more than it looks. A few lessons learned building this out: The entire tag must stay on a single line and in a common font — if it wraps across a line break during merge or PDF conversion, Adobe won’t recognize it, and the raw tag text stays visible instead of becoming a field. Field type directives are limited to what Adobe actually supports (signature, date, initials, etc.) — leaving the type off entirely creates a plain fillable text field, which is what was used for the banking detail fields here. Converting the merged Word document to PDF before sending it to Adobe Sign tends to produce more consistent tag detection than sending the raw .docx. Because the tags are static text baked into the template, no extra configuration is needed in Power Automate to "activate" detection — it happens automatically the moment the document is sent to Adobe Sign for signature. Step 3: Sending the Contract for Signature Once the Word template is fully populated, the flow hands it off to Adobe Acrobat Sign using the Create an agreement from a file content and send for signature action — passing the merged file straight through, along with the signer's name, email, and role. At this point, two things happen simultaneously: a) The customer's Contact person receives … Continue reading From Quote to Signed Contract in Minutes: Automating Adobe Acrobat Sign Integration for an Australia based Linen and Garments company →

From Quote to Signed Contract in Minutes | Cloudfronts DocuSign Blog Summary Automated end-to-end contract generation and digital signing for an Australia-based commercial linen and garment services company using Dynamics 365 Sales, Power Automate, and DocuSign. Eliminated manual contract preparation and PDF email workflows, replacing them with a one-click process triggered directly from the Dynamics 365 Quote record. Integrated DocuSign envelope creation, recipient assignment, and signature tab placement — all orchestrated through Power Automate cloud flows. Enabled real-time contract status tracking and automatic archival of signed PDF contracts back into SharePoint, linked directly to the originating Quote. Reduced contract turnaround time from days to hours, allowing the sales team to focus on customer relationships rather than administrative paperwork. Delivered a seamless customer experience — recipients receive a professionally formatted DocuSign email and can sign digitally from any device. Table of Contents 01 Summary 02 Introduction 03 The Business Problem 04 The Solution 05 Implementation 06 Business Impact 07 FAQs 08 Conclusion Introduction In industries where service agreements govern weekly delivery schedules, pricing structures, and compliance obligations, the speed and accuracy of contract execution can directly impact revenue and customer satisfaction. For commercial textile and linen services businesses in Australia, every signed contract represents a new route, a new customer, and a new revenue stream. Yet for many organisations, the final leg of the sales journey — converting an approved quote into a signed, legally binding contract — remains a surprisingly manual, error-prone process: exporting Word documents, emailing PDFs, chasing signatures, and manually filing returned documents. This blog documents how we at Cloudfronts transformed that process for a leading Australian commercial linen and garment services provider — deploying a fully automated DocuSign integration within Microsoft Dynamics 365 and Power Automate to take contracts from generation to signature without any manual intervention. The Business Problem Our client operates across multiple depots in Australia, servicing hotels, aged care facilities, hospitality venues, and healthcare providers with regular linen and garment delivery contracts. Their sales team works within Dynamics 365 Sales Hub, managing quotes that detail complex pricing, delivery schedules, weight-based charges, and product schedules. Before the integration, the contract signing process looked like this: A sales representative would generate a contract Word document from a template. The document was manually reviewed and converted to PDF. The PDF was emailed to the customer’s contact for signature. The customer would print, sign, scan, and return the document. The signed document would be manually uploaded to SharePoint and linked to the quote. This process introduced several critical pain points: Delays of 3–7 business days waiting for customer signatures. Inconsistent document versions being sent to customers. No visibility into whether a contract had been opened, reviewed, or signed. Risk of lost or misplaced signed documents. Significant administrative burden on the sales team. The business needed a solution that was seamless for both their internal team and their customers — something that could be triggered with a single action and would handle everything from document preparation to legally valid digital signature collection and storage. The Solution We designed and implemented a fully automated contract signing workflow that integrates Dynamics 365 Sales, Microsoft Power Automate, SharePoint, and DocuSign. The solution covers the entire lifecycle of a contract — from generation to signing to archival. Key Components Dynamics 365 Sales HubCentral system for quote and customer management. Power AutomateOrchestration layer connecting Dynamics 365, SharePoint, and DocuSign. SharePointDocument storage for generated and signed contracts. DocuSignDigital signature platform for legally binding contract execution. How It Works — At a Glance The solution is driven by two connected Power Automate flows: Send Contract Flow — Triggered manually from the Dynamics 365 Quote record. Retrieves the contract document from SharePoint, creates a DocuSign envelope, adds the contract document and recipient, places signature/name/date tabs, and sends the envelope. Receive Signed Contract Flow — Triggered automatically when the DocuSign envelope is completed. Retrieves the signed PDF from DocuSign and saves it to the same SharePoint folder, linking it back to the quote for a complete audit trail. Implementation 1 Step 1 Generate the Contract from Dynamics 365 The process begins in the Dynamics 365 Sales Hub on an approved Quote record. The sales representative clicks the Create Contract button in the command bar. This action triggers a workflow that generates a Service Contract Word document using the quote data and saves it to a dedicated Contracts folder in SharePoint, organised under the Quote number. Once generated, a confirmation dialog appears prompting the user to Open Contract for review before sending. The contract document is auto-named with the Quote ID and a timestamp, ensuring version control and traceability. 2 Step 2 Send the Contract for Signing After reviewing the document, the representative clicks Send Contract from the same Quote record. This triggers the main Power Automate flow — To send Contract Document to Customer for DocuSign. The flow executes the following steps: Compose Quote ID — Extracts and formats the Quote identifier. Get document location related to quote — Uses a FetchXML query against the SharePoint Document Location entity in Dataverse to locate the correct SharePoint folder linked to the Quote. Get Quote, Get Customer, Get Contact — Retrieves the customer’s full name and email address from Dynamics 365 for use as the DocuSign recipient. Initialise variables — Sets up Envelope ID, Recipient ID, and Parent Site location for downstream use. Iterate and locate the contract file — Loops through the SharePoint document library, resolves parent locations, retrieves file content, properties, and metadata. Create DocuSign Envelope — Creates an envelope with the subject line ‘DocuSign: Review & Sign the Contract Document’ and a personalised email body addressed to the customer contact. Add Document to Envelope — Attaches the contract Word document (encoded as Base64) to the envelope as a DOCX file. Add Recipient — Adds the customer contact as a signer with their full name and email from Dynamics 365. Add Signature Tabs — Places signature & other fields expaected to be filled by the recipient on … Continue reading From Quote to Signed Contract in Minutes: Automating DocuSign Integration for an Australia-Based Commercial Laundry Services Company →

Summary – What You Will Learn The benefits of moving from spreadsheets and manual tracking to real-time updates Field sales teams are constantly interacting with customers, distributors, contractors, and regional partners. These conversations often include important information such as pricing discussions, customer requirements, upcoming projects, and potential opportunities. However, in many manufacturing organizations, these interactions are not properly recorded. Information is often stored in notebooks, spreadsheets, or simply remembered by the salesperson. Over time, this creates a lack of visibility for managers and makes it difficult to understand what is happening across different territories. This blog explains how organizations can use Microsoft Dynamics 365 Sales to track field activities in a structured way and improve visibility into sales engagement and productivity. The Challenge The Field Sales Visibility Problem Field sales in manufacturing are highly relationship driven. Sales representatives regularly visit distributor branches, customer sites, and regional offices to maintain relationships and identify opportunities. But many of these interactions are never formally captured. This creates several challenges: a. No Interaction History Customer discussions and visit details are not recorded, making it difficult to track past conversations or commitments. b. Limited Visibility Across Teams Other team members and managers cannot easily see what has already been discussed with a customer. c. Difficulty Measuring Territory Engagement Managers may not know which territories are actively engaged and which areas need more attention. d. Missed Follow-Ups and Opportunities Potential opportunities discussed during visits may never be tracked properly in the sales pipeline. As a result, the CRM only reflects part of the sales activity, while many important field interactions remain invisible. The Solution Building a Structured Field Activity Process The goal is not to add extra administrative work for sales teams. Instead, the focus is on making activity tracking quick, simple, and useful. 1. Tracking Branch Visits and Customer Meetings Organizations can create a simple “Branch Visit” activity framework within the CRM to capture key field interactions such as: During each visit, sales teams can record useful details like: This helps create a consistent record of customer engagement across the organization. 2. Enabling Quick Mobile Updates Using the mobile capabilities of Microsoft Dynamics 365 Sales, sales teams can log activities directly from their phones immediately after meetings or visits. The process is simple and quick, helping improve CRM adoption without disrupting the sales team’s workflow. 3. Connecting Activities to Customers and Opportunities Recorded visits can be linked directly to customer accounts and ongoing opportunities. This allows teams to: 4. Turning Activities into Insights Once activities are consistently captured, organizations can generate useful reports such as: Customer Activity Reports These reports combine: into a single customer timeline, helping teams understand how frequently accounts are being engaged. Before vs after: what changes with a CRM The shift from manual tracking to structured CRM logging is less about technology and more about having one shared version of the truth. Area Without CRM tracking With CRM tracking Visit records Notebooks, memory, or nothing Logged on mobile, linked to the account Manager visibility Relies on what reps choose to share Real-time dashboard across all territories Team handovers Rep briefs colleague verbally, gaps guaranteed Full interaction history visible to the whole team Follow-ups Tracked in spreadsheets or not at all Tasks created in the CRM, assigned and time-stamped Territory review Guesswork or anecdote Activity reports per rep, per region, per account Salesperson Activity Reports These reports help managers: Using Microsoft Power BI, this information can also be displayed through dashboards for easier visibility and decision-making. Business Impact / Results When field activities are properly tracked, organizations gain much better visibility into their sales operations. Key benefits include: Managers can now: Most importantly, field sales productivity becomes visible, measurable, and easier to manage. For implementation within Microsoft Dynamics 365 Sales: These configurations help keep the process scalable while remaining easy for teams to use. FAQ Section a. What is a Branch Visit activity? A Branch Visit activity is a structured way to record field interactions such as distributor visits and customer meetings within the CRM. b. How does this improve productivity? It helps organizations track customer engagement more effectively and gives managers better visibility into sales activities. c. Can this data be visualized in dashboards? Yes. Using Microsoft Power BI, organizations can create dashboards to monitor territory activity and sales engagement. d. How can companies improve CRM adoption among field teams? Keeping the process simple, mobile-friendly, and quick to update encourages better adoption across sales teams. e. What changes for managers? Managers can focus on coaching and customer strategy instead of chasing updates. This also reduces time spent collecting updates manually and improves overall visibility into sales activities across regions. To conclude, Field sales will always depend on strong customer relationships. However, managing those relationships should not rely on memory, spreadsheets, or disconnected notes. By using Microsoft Dynamics 365 Sales to track and structure field activities, manufacturing organizations can gain better visibility into customer engagement and sales performance. Instead of guessing productivity, managers can rely on real-time data to understand how actively teams are engaging with customers and where improvements are needed. A structured field activity process helps organizations become more organized, more informed, and better prepared to manage sales growth. Connect with CloudFronts to get started at transform@cloudfonts.com Author Bio Cassandra Rodrigues is a D365 CRM Consultant specializing in CRM solutions and sales process optimization for manufacturing organizations. She focuses on helping businesses improve visibility, streamline operations, and build practical solutions using Microsoft Dynamics 365 Sales. If you’re looking to improve visibility into field sales activities and build a more structured, data-driven sales process, feel free to reach out to CloudFronts to learn how these solutions can be implemented within your organization.

Summary : In this blog, you will learn: Field sales teams generate some of the most valuable business insights during distributor visits, site meetings, and customer discussions. These interactions often include pricing feedback, upcoming opportunities, and competitor information. But in many manufacturing organizations, this information is never formally captured. It stays in personal notes or memory and is lost when teams change or time passes. The result? Leadership lacks visibility into what is actually happening in the field. This blog explains how organizations can solve this by using Microsoft Dynamics 365 Sales to turn everyday field interactions into structured, measurable data. The Challenge The Field Sales Visibility Problem Field sales in manufacturing is highly relationship-driven. While this builds strong customer connections, it also creates a major gap in tracking and visibility. Key challenges include: This leads to a situation where the CRM reflects only partial activity, missing the interactions that actually drive business. The Solution Building a Structured Field Activity System The goal is not to increase administrative work, but to make activity tracking quick, simple, and useful. 1. Introduce a “Branch Visit” Activity FrameworkCreate a structured way to capture key field interactions such as: Each visit can include: This ensures every interaction is recorded in a consistent and useful format. 2. Enable Quick Mobile UpdatesUsing the mobile capabilities of Microsoft Dynamics 365 Sales, sales teams can log visits immediately after meetings. The process is simple and takes less than a minute, making it easy to adopt without disrupting their workflow. 3. Connect Activities to Customers and OpportunitiesAll recorded visits are linked to customer accounts and ongoing deals. This allows: 4. Turn Data into InsightsOnce activities are consistently captured, organizations can generate reports such as: With Microsoft Power BI, this data can be visualized into dashboards that clearly show trends and performance. Business Impact / Results When field sales activities are properly tracked, the impact is immediate and measurable: Managers can now: Most importantly, field sales productivity becomes visible, measurable, and manageable. Technical Deep-Dive (Simplified) For implementation within Microsoft Dynamics 365 Sales: These configurations ensure the system is scalable while remaining easy for sales teams to use. FAQ Section a. What is a Branch Visit activity?It is a structured way to record field interactions like distributor visits and customer meetings, ensuring all key details are captured in the CRM. b. How does this improve productivity?It connects daily activities with actual sales outcomes, helping managers track performance and identify gaps. c. Can this data be visualized?Yes, using Microsoft Power BI, organizations can create dashboards to monitor performance across regions and teams. d. How do you ensure sales teams actually use the system?By keeping the process fast, simple, and beneficial so it saves time rather than adding extra workz To conclude, Field sales will always be driven by relationships but managing those relationships should not rely on memory or manual tracking. By using Microsoft Dynamics 365 Sales to capture and structure field activities, organizations can transform how they measure productivity. a. What was once invisible becomes clear.b. What was once assumed becomes measurable. This shift allows leadership to make better decisions, improve sales performance, and strengthen customer relationships. If you’re looking to bring visibility and structure to your field sales operations, now is the time to adopt a smarter, data-driven approach. The author is a D365 CRM Consultant specializing in sales process optimization for manufacturing organizations. She focuses on helping businesses implement practical, user-friendly solutions using Microsoft Dynamics 365 Sales to improve visibility, efficiency, and performance. Connect with CloudFronts to get started at transform@cloudfonts.com

SummarySales tax configurations in Microsoft Dynamics 365 Finance and Operations can go beyond simple percentage calculations. In scenarios where taxes are layered or interdependent, businesses often require a tax-on-tax (cascading tax) setup. This blog explains how to configure an 18% primary tax and an additional 5% tax calculated on top of it, ensuring accurate, automated, and compliant tax calculations for complex service-based industries like Oil & Gas. Sales Tax Setup in Microsoft Dynamics 365 Finance & Operations (18% + 5% Tax-on-Tax) In global and industry-specific implementations, taxation is not always flat. Many organizations, especially in regulated sectors, require layered tax calculations where one tax is applied on top of another. In one such implementation within Microsoft Dynamics 365 Finance and Operations, this configuration was successfully used for a service-based company in the Oil and Gas industry. The requirement was straightforward but technically nuanced: a. Apply a primary tax of 18% on the service valueb. Apply an additional 5% tax on the total amount after the first tax This type of setup is commonly required when: a. Multiple statutory taxes are interdependentb. Regulations mandate tax calculation on already taxed valuesc. Service contracts involve multi-layered billing structures By configuring this correctly, businesses can eliminate manual calculations and ensure compliance. Understanding the Requirement The logic follows a cascading structure: a. First, calculate 18% on the base amountb. Then, calculate 5% on (Base Amount + 18% tax) Example Calculation: a. Item price = ₹100b. 18% tax = ₹18c. 5% tax on ₹118 = ₹5.9d. Total tax = ₹23.9e. Final amount = ₹123.9 This demonstrates how the second tax depends on the first, making configuration accuracy critical. Step-by-Step Configuration 1. Create Sales Tax CodesNavigate to:Tax > Indirect taxes > Sales tax > Sales tax codes a. Create Tax Code 1Name: Tax18Percentage: 18% b. Create Tax Code 2Name: Tax5Percentage: 5% 2. Configure Tax-on-Tax For Tax5 (5%): a. Enable: Calculate tax on taxb. Select base tax: Tax18 This ensures Tax5 is calculated on the net amount + Tax18. 3. Create Sales Tax Group Navigate to:Tax > Indirect taxes > Sales tax > Sales tax groups a. Create: SALES_TAX_GROUPb. Add:i. Tax18ii. Tax5 4. Create Item Sales Tax Group Navigate to:Tax > Indirect taxes > Sales tax > Item sales tax groups a. Create: ITEM_TAX_GROUPb. Add:i. Tax18ii. Tax5 5. Assign Tax Groups a. Assign the Item sales tax group to the itemb. Ensure correct mapping in transactions Tax Calculation Flow Step Amount Base Amount ₹1000 GST18 (18%) ₹180 GST5 (5% on 118) ₹59 Total Tax ₹239 Final Amount ₹1239 a. Tax-on-tax must always be configured on the dependent tax (5%)b. Sequence of tax codes directly impacts calculation accuracyc. Always validate through Sales Order → Invoice → Tax detailsd. Perform complete testing in Sandbox before Production deployment Conclusion Tax-on-tax configuration in Microsoft Dynamics 365 Finance and Operations is a powerful capability that enables businesses to handle complex, cascading tax requirements with precision. By structuring tax dependencies correctly: a. The base tax (18%) is calculated firstb. The dependent tax (5%) is automatically applied on the cumulative amount This ensures: a. Accurate financial reportingb. Regulatory compliancec. Zero manual intervention For industries dealing with layered taxation models, this approach is not just helpful-it is essential. I hope you found this blog useful. If you would like to discuss anything further, feel free to reach out to us at transform@cloudfronts.com.

One of the small but frustrating limitations in Microsoft Dynamics 365 is how subgrids handle record creation. If you’ve worked with Opportunities, Quotes, Orders, or any parent–child setup, you’ve probably experienced this: You need to add multiple related records. The system allows you to add them one at a time. Click New. Save. Repeat. It works, but it’s slow, repetitive, and not how users naturally think. Over time, that friction adds up. The Real Problem In our case, an Australia-based linen and garments company, was using Dynamics 365 to manage sales opportunities for hospitality and healthcare clients. Their sales team regularly needed to add multiple products — such as linen packages, garment services, and rental items, to a single Opportunity. These products were organized by categories like: A typical deal didn’t include just one item. It often included five, ten, or more products across different categories. However, the out-of-the-box sub grid experience required them to: There was nothing technically broken. But from a usability perspective, it wasn’t efficient — especially for a fast-moving sales team handling multiple client proposals daily. What they really wanted was simple: Select products by category → Choose multiple items → Add them in one go → Move on. That capability simply wasn’t available within the standard sub grid behavior. Approach Instead of forcing users to follow the repetitive process, we extended the form with a custom solution. We built a lightweight HTML-based interface embedded inside the form. This interface: Once the user confirms their selection, the chosen records are sent to a custom server-side process. From the user’s perspective, the experience becomes: Open selector → Choose multiple items → Click once → All records created. Simple. Fast. Intuitive. What Happens Behind the Scenes While the interface feels straightforward, the actual processing is handled securely on the server. When users submit their selection: This ensures the solution is: The business logic remains centralized and controlled, not exposed on the client side.file. Why This Matters The improvement may seem small at first. But consider users who perform this task daily. Reducing repetitive actions saves time, lowers frustration, and improves overall efficiency. More importantly, it makes the system feel aligned with how users actually work. Instead of adapting their workflow to system limitations, the system adapts to their workflow. That’s where meaningful customization adds value. The Outcome By combining: We created a smooth bulk record creation experience within Dynamics 365. The platform remains intact. The business logic remains secure, and the user experience becomes significantly better. And sometimes, that’s exactly what good system design is about, not rebuilding everything but removing friction where it matters most. We hope you found this article useful. If you would like to explore how AI-powered customer service can improve your support operations, please contact the CloudFronts team at transform@cloudfronts.com.

In Microsoft Dynamics 365 CRM, every Case (Incident) record comes with a default Ticket Number. Microsoft generates it automatically, and while that’s fine for basic tracking, it usually doesn’t survive first contact with real business requirements. Users want meaningful Case IDs—something that actually tells them what kind of case this is, what service it belongs to, and where it came from. Unfortunately, since Ticket Number (ticketnumber) is a Microsoft-managed field, you can’t just slap a custom format on it using configuration alone. That’s exactly where a Pre-Operation plugin comes in. This blog walks through a real production use case where we customize the default Case ID format without breaking Microsoft’s auto-numbering, and without creating race conditions or duplicate numbers. Use Case Table: Case (Incident) Field: Ticket Number (ticketnumber) Requirement: Execution: Why Pre-Operation Microsoft generates the Ticket Number before the Create operation completes. In Pre-Operation, we can: This gives us: The Custom Ticket Number Format The final Case ID looks like this: Example: Plugin Logic Overview Here’s what the plugin does, step by step: The Plugin Code Plugin Registration Details Message: Create Primary Entity: Case (incident) Stage: Pre-Operation Mode: Synchronous Filtering Attributes: Not required. To conclude, customizing a Microsoft-managed field like Ticket Number often sounds risky, but as you’ve seen, it doesn’t have to be. By letting Dynamics 365 generate the number first and then reshaping it in a pre-Operation plugin, you get the best of both worlds. We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

We are delighted to announce that Gouge Linen and Garment Services Partners with CloudFronts for the implementation of Dynamics 365 Sales and Customer Services.  Founded in May 1945, Gouge Linen and Garment Services is a leading 100% Australian-owned industrial laundry provider, strengthening its role as a trusted partner across healthcare, aged care, hospitality, manufacturing, and food production sectors. Backed by state-of-the-art facilities and a dedicated logistics network, the company delivers high-quality linen, garment, mat, and towel services with exceptional reliability and efficiency. Gouge remains committed to sustainability through advanced water-saving systems, energy-efficient operations, and responsible business practices, reinforcing its strong reputation for service excellence and community impact.  Learn more about them at https://www.gouge.com.au/  Gouge Linen currently relies on excel-based quoting, manual freight costing, and fragmented data stored across ABS/Oracle BI. This lack of integration limits visibility across departments, creating inefficiencies, delays, and scalability challenges. CloudFronts will deploy Microsoft Dynamics 365 Sales with a CPQ (Configure, Price, Quote) process to automate quote generation, team to streamline sales, service, and route costing workflows. The solution will deliver real-time visibility into inventory, production costs, and freight data, enabling faster, data-driven decisions across the organization.   The implementation will reduce quote turnaround time from days to under an hour, improve coordination between sales, operations, and logistics teams, and enhance overall customer experience.  On this occasion, Priyesh Wagh, Practice Manager at CloudFronts, stated:  “ We look forward to partnering with the Gouge team as we initiate the first phase of their Dynamics 365 Sales and Customer Service implementation, which will evolve into a comprehensive quotation engine. This initial rollout will establish a strong foundation for an integrated sales-to-service platform, with the potential to extend into billing capabilities in the future. We’re excited to collaborate with the Gouge Linen and Garment Services team on this transformation journey.” About CloudFronts  CloudFronts is a global AI- First Microsoft Solutions & Databricks Partner for Business Applications, Data & AI, helping teams and organizations worldwide solve their complex business challenges with Microsoft Cloud, AI, and Azure Integration Services. We have a global presence with offices in U.S, Singapore & India.    Since its inception in 2012, CloudFronts has successfully served over 200+ small and medium-sized clients all over the world, such as North America, Europe, Australia, MENA, Maldives & India, with diverse experiences in sectors ranging from Professional Services, Financial Services, Manufacturing, Retail, Logistics/SCM, and Non-profits.     Please feel free to connect with us at transform@cloudFronts.com