Connect the account's call route to the team that answers it
Google Ads call-asset audits for in-house teams: establish coverage, the correct number and a measurable call outcome
Interpret the presence finding within its actual scope, confirm the business route and coordinate call handling. Prepare precise campaign asset changes while keeping verification, reporting and commercial outcomes distinct.
Define the business reason to offer a call
A call-asset audit should connect the account's configuration with a real business route. The team may want customers to book a service, ask about product compatibility or discuss a complex purchase. Those purposes can require different numbers, hours and handling arrangements. Begin by identifying the intended conversation and the team that can answer it. An enabled asset is useful only within that context. The review should not treat a phone number as a generic decoration that every campaign needs regardless of the offer or operational capacity.
Define what the customer should be able to accomplish. A sales line and a support line can both be legitimate business numbers while serving different needs. A campaign promising a quotation should not direct callers to a route that cannot provide one. The media owner should confirm the purpose with the operational team before preparing an account change. The audit's presence finding can prompt this review, but it does not establish the actual route, the staff's knowledge or the quality of the conversation.
A completed review should leave an understandable decision: retain the existing route, attach a confirmed asset, create a new one or remove an inappropriate association. It should also identify the measurement question and next observation. A structural pass does not prove every call was answered or commercially valuable. Conversely, a missing call asset does not prove the business receives no phone enquiries through other paths. Keep the account observation and the operational decision connected without expanding either into a universal statement about the business.
Understand the call asset's role
Call assets make a business phone route available with eligible ads. The provider distinguishes their associations, reporting options and conditions of appearance. Google's call-asset guidance explains that role. The team should distinguish a stored and associated asset from an observed call opportunity in delivery. An asset does not appear with every impression, and its presence alone cannot demonstrate how many people used the route.
The phone number is an input with an operational consequence. It should represent the intended business and reach the appropriate team. A syntactically acceptable number is not proof of that relationship. Nor does the account audit establish whether a caller can complete the intended task. The in-house review should gather those facts from the people responsible for the route. This is a separate responsibility from selecting the exact asset and campaign association for an edit.
Keep expected benefits as objectives rather than guaranteed results. The team may want easier access to a helpful conversation, but creating a call asset does not certify increased conversions or revenue. The appropriate evidence depends on the question: stored content for configuration, a route test for a particular operational observation and selected metrics for later performance. A clear record lets the owner see what has been established. It also prevents the provider feature's general purpose from being presented as a confirmed result in this account.
Read the audit's conversion-based trigger
The current ppctor call-asset card is triggered when the analysed conversion setup includes a phone-call-lead category action. That setup comes from enabled conversion actions and excludes locked provider-managed families through the analysis filter. The trigger does not require the action to be primary. A secondary phone-call action can therefore make the card applicable. This is an implementation-specific selection, not proof that the account actively optimises toward calls or that every possible phone-related conversion type has been reviewed.
If the card is absent, do not conclude that phone calls have no relevance to the business. The relevant actions may be outside the selected setup, use another category or belong to a locked family that the analysis excludes. The business may also have a call-route question unrelated to a configured conversion action. Ask the actual question and retrieve the appropriate evidence. A conditional audit card is a way to surface one configuration relationship, not a complete inventory of every operational need or call measurement arrangement.
The category should not be treated as verified lead quality. It describes the configured action, while the business defines what a valuable conversation means. If the team needs to inspect action names, types, sources or primary status, use those fields explicitly. Do not infer them from the card's existence. A precise reply can explain why the finding appeared and what it checked. That helps an in-house owner reconcile the audit with the account without reading a technical list of conversion enums.
Interpret the presence finding precisely
For an applicable card, the current check looks for a call type among enabled account associations or among the selected campaign coverage. Its success condition is any detected call coverage in those sources. It does not require every relevant campaign to have an appropriate route. One selected campaign-level call asset can therefore satisfy the card while another campaign still needs a specific review. Keep the distinction between account-level presence and campaign-by-campaign suitability visible in the conclusion.
The campaign coverage population consists of enabled campaigns that recorded impressions in the audit period, excluding Local Services and Smart campaign types in that read. An account-level association is observed separately. A newly staged campaign without impressions can have a call asset outside the served-campaign comparison. The team should interpret the current finding at its actual scope rather than label that asset nonexistent. If the user asks about a named campaign, inspect its exact association instead of relying on the account's any-present result.
The card identifies a structural relationship between analysed phone-call measurement and detected asset coverage. It does not return the number, hours or call-reporting settings as part of this test. A useful response can state that presence was detected and then identify the next question if the user wants operational assurance. Avoid translating Present into every campaign can call the correct sales team. That statement needs more evidence than the card supplies, even when the configuration looks reassuring.
Preserve the coverage limitations
The current association reads supporting this call finding cover account and selected campaign sources. They do not establish a complete inventory of ad-group-only call associations. A user can therefore have a relevant lower-level asset outside the card's observations. Scope should be checked before interpreting a missing result. Provider hierarchy can also affect the actual route, so a broader association does not independently establish which number applies at a more specific level. Follow the actual resource when the question concerns a particular group.
A detected enabled association is not a test of phone eligibility, successful routing or actual appearance. The audit does not call the number, inspect staffing or verify every provider requirement. A number can be present while needing another review. The team should name the observation precisely rather than declare the phone system complete. This keeps a useful structural finding from becoming a certificate about operations the app has not inspected. The next task can then be assigned to the appropriate owner.
The conversion trigger has its own boundary as well. A card based on one analysed category does not list every call-related source or confirm its reporting configuration. These limits should remain explicit in an internal record. A colleague who asks why a call action did not trigger the card may need its type, status and analysis eligibility inspected. A colleague asking which number serves needs the actual relationship and asset content. Different questions should receive different evidence rather than the same generic presence answer.
Distinguish missing assets from unavailable evidence
The call finding depends on both extension coverage and conversion-action evidence. If those required reads fail, the audit's dependency handling marks the finding unavailable. That is different from a completed applicable check finding no detected call asset. The team should resolve access or provider retrieval before treating an empty fallback as configuration. An unavailable card does not establish that a number should be created, and a duplicated asset is not a valid response to missing evidence.
Successful emptiness can also have several meanings. The selected conversion setup may contain no trigger category, the selected coverage may contain no call association or the campaign population may be empty. The reply should preserve the actual condition. Do not turn an absent card into all calls configured correctly. If the business asks a direct call-route question, use a scoped read even when the conditional audit is not applicable. The audit's selection should not prevent the assistant from answering an independently valid account question.
Assign evidence recovery separately from operational review. The media owner can obtain the intended current read, while the phone-route owner confirms where the number leads. These tasks can proceed with clear boundaries, but neither substitutes for the other. A remembered number does not prove its association is current, and a successful association read does not prove the call is answered. The record should identify which fact remains unestablished so the next action answers the original question instead of merely producing another status message.
Confirm the intended business number
The owner should provide or confirm the actual business number and its country context. Do not select a number merely because it appears elsewhere in the account or on an old page. The route may have changed, or the number may belong to a different department or location. A campaign promoting a specific service can need a specialised route. The media owner should preserve that commercial context before preparing creation or attachment. The exact content matters as much as the existence of the asset.
Use provider requirements for the actual number and advertised business. The convenience adapter's format checks are not proof of ownership or provider verification. A local regular-expression match can accept input while additional provider requirements remain unresolved. Do not tell the user the number is verified because preparation succeeded. The team should establish the operational route through its owner and inspect provider state where necessary. This separates acceptable request construction from the broader question of whether the asset is eligible and appropriate.
A route test can establish a narrow observation, such as whether the number reaches the intended menu or team at the time checked. It does not prove every future call will succeed. Record the useful result without overstating it. The business can also confirm how the route is maintained and who handles changes. If a new number is needed, the account proposal should show it exactly in a clear review row. Do not publish unrelated personal contacts or customer caller details as part of ordinary Slack output.
Coordinate call handling with the campaign
The campaign's promise should match what the receiving team can provide. A route that answers product questions may not be equipped to make appointments, and a central switchboard may need a clear transfer path for a specialised service. The in-house review should establish this relationship directly. Call-asset presence cannot tell the media owner whether staff understand the promoted offer. A brief operational handoff can identify the campaign purpose, likely enquiry and expected next step without exposing individual customer conversations.
Handling capacity is a business decision distinct from asset configuration. A team may want a phone route for high-consideration enquiries while preferring another path for routine orders. The review should not assume more calls is always the desired outcome. Ask which conversations are useful and which team can respond. This can lead to a narrower campaign association or a deliberate decision not to add a call asset in a particular context. The audit's general relationship to phone conversions should inform, not override, that commercial choice.
Keep routing changes coordinated across the website and advertising where relevant. A website number may differ deliberately from the ad asset, but the team should know why. An operational change can require an account update, while an account change can leave the receiving process unchanged. The record should identify both sides. If the business changes department responsibilities, revisit the route before continuing to use the old asset simply because it remains enabled and the audit still reports presence.
Treat hours and schedules as explicit settings
Call availability should reflect the business's intended handling arrangement. Some routes are staffed only during certain hours, while others have a deliberate after-hours process. Establish which applies before preparing a change. The presence audit does not inspect schedules or prove that the displayed route coincides with staffing. A team should not assume a campaign's general schedule also establishes every call-specific condition. Review the actual settings needed for the operational decision.
The provider supports call-asset scheduling, but the current convenience creation adapter discussed here accepts country code and phone number rather than a schedule plan. A request to create a route only during specified hours needs an actually supported setting operation for that requirement. It should not be silently reduced to a number-only creation. If the current path cannot prepare the schedule, explain that boundary and keep the remaining task visible. The owner must know what the proposal does and what it does not establish.
Time-zone context is important when colleagues coordinate regional routes. Use the intended account and operational context for the actual schedule review. Avoid promising universal local-time behaviour from a country code alone. The number's country, campaign targeting and staffed hours are separate facts. A clear internal plan can state the intended availability, owner and precise implementation task. Once the setting is changed, verify that configuration separately from any later call-handling observation or performance assessment.
Assign operational and media ownership
The media owner selects and verifies the account operation, while the operational owner confirms the number and handling arrangement. A measurement owner can assess how the chosen action is counted. These roles may belong to the same person in a small team, but the evidence remains separate. The review should avoid asking the media team to certify a telephone process it has not tested, or asking the receiving team to interpret account associations it does not manage.
A useful task should name the campaign, intended call purpose, selected number and exact question. It can ask an operations colleague to confirm routing, a measurement colleague to identify the call action or the media owner to prepare an attachment. Each task should have a completion condition. This is more effective than a generic fix call tracking request that combines content, routing, reporting and conversion roles without identifying what is actually wrong. The audit finding should help divide the work into answerable questions.
Preserve the handoff as work progresses. Confirming the number does not mean it has been created in the account. Creating an asset does not mean reporting is configured. A reporting read does not prove the operational route is appropriate. The review record should show the current stage and the next owner. This allows a conversation to resume after delays without repeating unrelated discovery or creating another asset because the earlier decision was no longer visible.
Separate call clicks, calls and conversions
A call-related click, an actual phone conversation and a counted conversion are different measures. The provider exposes several phone-call tracking approaches, including ad routes, website routes and imported outcomes. Google's phone-call conversion guidance explains those distinctions. The team should identify which action and measure the requested report uses. A click count should not be described as every call answered, and a conversion count should not automatically be labelled unique customers.
The business definition matters as well. The team may count a call according to configured criteria, or import a later outcome from another system. That definition can be useful while still differing from a sales conversation or purchase. The audit's category-based trigger does not inspect all those implementation details. Retrieve the relevant fields and evidence when the user asks how calls are counted. Do not invent a duration threshold or source simply because the action has a familiar name.
Keep operational and measurement observations alongside each other. A route test can confirm where a call goes, while a provider report can show the selected recorded measure. Neither proves the other. If the team wants to assess sales quality, define the actual outcome and source needed rather than infer it from a lead category. The assistant can help formulate the question, but the answer should follow available evidence. This keeps an apparently simple call report from making unsupported claims about the people and conversations behind the numbers.
Use primary call outcomes and their values deliberately
For reporting that requests primary call conversions, include the relevant primary call actions and exclude secondary actions from that primary aggregate. Call actions can also record conversion value. Do not assume that value is reserved for purchase-category actions. The report should identify its selected action population and value definition. A category or action name alone is not enough to determine whether value represents a fixed business estimate, an imported sale or another configured measurement.
A broader total of all primary conversions can include calls alongside other primary outcomes. A primary purchase-only total has a different selection. Preserve the user's requested definition instead of silently replacing it with whichever column is easiest to retrieve. If the user names a specific action, use its exact evidence. The presence audit's trigger includes eligible analysed phone-call actions regardless of primary status, so its applicability is not itself proof that the primary reporting population contains call conversions.
Role, counting and value settings are separate questions. Changing an asset association does not change an action's primary role or counting method. Changing a role does not repair the number or reporting implementation. The team should assess each setting through an actually supported operation and its valid target. Keep locked provider-managed actions distinct from editable actions; do not infer editability from a friendly display name. A clear proposal identifies the precise requested field rather than bundle unrelated measurement changes into call-asset creation.
Review call-reporting configuration separately
The existence of a call asset and a phone-call conversion action does not independently prove the complete reporting setup works. The actual source, relevant settings and implementation determine what can be observed. The presence card does not verify call-reporting activation, forwarding behaviour or every measurement dependency. If the team asks whether calls are tracked, define the intended route and action, then inspect the appropriate configuration and results. Do not use the asset's presence as a complete measurement certificate.
Provider features and geographic availability should be checked for the actual implementation where they matter. A number's country code is not proof that every reporting feature is available or enabled. The assistant should not promise call recording, transcripts or quality assessment merely because Google offers phone-related products. Those capabilities require their own evidence, access and supported tool path. Keep the question scoped to what the user requested, and distinguish provider availability from something the current app has retrieved or configured.
A useful measurement review can end with a specific unresolved dependency. The owner may need to inspect an action setting, confirm a website implementation or assess an imported outcome. Record that task separately from a verified asset change. This avoids presenting an incomplete measurement workflow as fixed simply because the campaign now has an enabled relationship. It also prevents needless asset creation when the existing number is correct and the actual problem belongs to reporting rather than the route itself.
Keep Analytics event comparisons explicit
A Google Ads call conversion does not have a universal corresponding Analytics event. Sites can use different events for phone-link clicks or other lead interactions, and those events may describe a different stage from a completed call. If the user requests a comparison, select the corresponding event explicitly and explain the measures. The assistant can suggest a likely event by name for confirmation, but the name is a clue rather than proof that the two sources represent the same underlying outcome.
Aggregated leads can include different primary lead categories without requiring a separate quality hierarchy invented from category names. The business should choose the Analytics lead event or event set appropriate to its request. A named Ads action can also be compared with a specified Analytics event. Preserve both names and the selected scope. The framework should support that correspondence rather than hard-code one phone event for every account. A site-specific mapping is a real part of the analysis, not an inconvenience to skip.
Cross-source charts need clear definitions as well as dates. A phone-link click series and a counted call-conversion series can be shown as a deliberate comparison, but the reply should not imply they are identical counts. Primary conversion value and revenue measures also need their proper populations. Revenue from all traffic divided by advertising cost is blended ROAS or MER. The assistant should retrieve the selected data and label it accurately, rather than refuse every useful comparison or combine mismatched measures without explanation.
Align current settings and dated performance
The audit reads current enabled associations and uses a served-campaign coverage population from its period. A performance report describes activity within requested dates. A campaign can have an asset now that was not associated earlier, or can retain historical call results after the route changed. Keep those observations separate. A current presence result does not reconstruct every historical number or association. If the team asks about a specific period, retrieve the evidence that actually describes that period and preserve the selected metric.
Campaign statuses can differ between current configuration and historical activity. The audit's coverage read should not become an implicit filter for every performance question. A paused campaign may have relevant results during the requested dates. Conversely, a newly enabled campaign can have little activity yet. The response should identify the population and completed dates in readable language. Do not confuse a current account review with last month's report or reuse an old period simply because another dashboard has a saved selection.
After a route change, define the later review deliberately. The team may want to assess selected calls, conversions, value or an operational observation. Comparing mismatched periods can obscure the result, while recent data may not yet answer every question. The verified asset state is one stage, not proof of commercial improvement. Keep the original rationale and measurement definition available so colleagues can assess what changed without attributing every subsequent movement to the attachment alone.
Follow an invented internal routing review
In an invented example, Sera Holt manages media for Birch Room Services. The audit's call finding is applicable because an eligible analysed phone-call action exists. A call asset is detected somewhere in the selected coverage, so the card passes. Sera still reviews the Installation campaign because its operational owner reports that enquiries should reach a specialised team. The account's any-present result did not establish that campaign's correct route. She retrieves the relevant relationship and asks the owner to confirm the intended business number.
The team identifies an existing asset for the specialised route and chooses to attach it to the campaign. A separate old campaign association is no longer appropriate and receives its own detachment proposal. The record states that the underlying asset remains available elsewhere. If staffed hours need a setting change, Sera treats that as a distinct supported-operation question rather than assume the attachment supplies a schedule. The proposal shows exactly which account relationships it will change.
After confirmation, configuration readback establishes the selected association states. The receiving team separately confirms the route observation, and the measurement owner reviews the selected primary call results at agreed dates. This is an invented process, not a customer result or a guaranteed increase in calls. The useful outcome is that the team knows which number belongs to the offer, which relationships changed and what evidence remains needed. One presence status no longer stands in for all those operational and measurement questions.
Use Slack for evidence and planning
Slack can make the review accessible to the colleagues who own the route. The user might ask whether a named campaign has a call asset, what number it uses or how many primary call conversions occurred. Those are different questions with different evidence. The assistant should retain established campaign context while retrieving the fields needed for the current request. A concise answer can name the campaign and business number without exposing asset IDs or unrelated account details.
Planning can also be conversational without provider calls. The assistant can help draft a call-handling brief, suggest how to explain the offer or identify questions for the operations owner from confirmed context. Those suggestions should remain labelled as reasoning. Current associations, action settings and performance need actual provider evidence. This distinction allows useful creative and organisational work while preventing imagined account facts. The user should be able to move from discussion to a precise proposal without every message triggering another broad scan.
The Slack audit workflow can surface the presence finding, while follow-up focuses on the actual campaign, asset or conversion action. A known attachment request does not require discovering every group to find a parent the asset does not have. The exact account ownership and relationship still need validation. Preserve context and target precision together. If the request remains ambiguous, ask one clear question about the missing resource rather than infer the wrong number from a familiar campaign name.
Prepare a new campaign call asset
The current campaign-extension creation adapter supports a call asset using a country code and phone number. It validates the accepted input format, prepares the new asset and attaches it to the selected campaign in the same provider mutation. Existing extensions are retained. The proposal should show both creation and attachment, and the number must be confirmed by the owner. This is a specific implemented operation, not a universal phone-system setup or an automatic configuration of every reporting feature.
The adapter records readback checks for the written country and number fields and for the exact enabled campaign association. The returned created asset reference anchors those checks. This matters when similar numbers or several assets exist. The visible proposal can display the number and campaign plainly, while the temporary and returned technical references remain internal. Structural validation and successful readback establish stored configuration; they do not prove the number is provider-verified, answered or connected to the intended staff.
This convenience creation path does not include every call-specific setting. Scheduling, reporting and other requested changes need their own supported operations where available. Do not silently omit them from a multi-step request, and do not claim they were configured because asset creation succeeded. If an existing-content correction is requested, select an actual supported edit path rather than create another asset without explaining that effect. The user should know whether the proposal creates a new resource, changes content or changes only a relationship.
Prepare existing attachment or detachment
For an existing call asset, the adapter reads the selected campaign's enabled call associations and the exact chosen asset. It checks ownership and type and requires a meaningful name or visible content for review. The asset's number can provide that recognisable label. This prevents attaching an unrelated asset from a different type or selecting a resource with no understandable target in the proposal. The owner should see the campaign and number that will be linked.
The adapter detects whether the desired relationship already exists. It avoids adding a duplicate association or attempting an unnecessary detachment. When change is needed, it prepares the exact relationship operation and a check of the intended association set. The result should distinguish an already-established state from a newly executed change. A redundant request can be resolved usefully without pretending another live operation occurred. This keeps the record accurate and avoids unnecessary provider mutations.
Detachment retains the underlying asset and does not remove every call route in the account. Other associations or levels can remain relevant, and the provider's hierarchy can affect the effective route. The visible proposal should therefore say which campaign relationship is removed. If the user wants a broader outcome, inspect that actual scope and prepare supported operations for it. One association change should not be presented as disabling all calls or deleting the phone number everywhere.
Present clear targets and approval steps
The live conversational edit happens after Confirm and Execute is clicked. Before that point, the message should state that no changes have been made yet and show the expiry. Each logical action needs a clear target and intended effect. For a new call asset, show the number, country context and selected campaign, then the creation-and-attachment effect. For an existing asset, show attach or detach distinctly. Avoid a technical paragraph that leaves the user unsure whether the number itself or only a relationship will change.
The proposal must fit the supported review safeguards and show the complete intended account changes. If it needs narrower requests, explain that requirement before any live edit. Do not execute an arbitrary subset while dropping the rest. A phone-route plan can include external operational work as well as live account changes; the proposal must identify which ones the tool will actually perform. The presence of an internal task in the discussion is not proof it belongs to the API execution sequence. Assign external work separately so each team can verify its own responsibility.
A clear progress state should acknowledge the click immediately while execution proceeds. The final message should prominently distinguish executed-and-verified changes from incomplete outcomes and show each requested result. Use meaningful campaign and asset content without IDs or undefined parent labels. A stored number or association should not be described as fully verified call handling. The owner should recognise exactly what happened and what remains from the comparison between the proposal and the result.
Verify configuration without certifying the phone journey
Configuration verification checks the fields and relationships requested by the proposal. Creation checks the returned asset's stored content and its campaign association; attachment and detachment check the intended relationship. These observations can establish a successful account edit. They do not test the receiving team, provider phone verification, reporting implementation or commercial quality. The success message can be clear about the configuration while keeping those broader tasks separate. This gives the owner useful certainty without claiming work the tool did not perform.
A broad audit rerun is not a substitute for exact readback. The account can continue to pass the any-present call finding after one campaign relationship is removed because another source still provides coverage. A new asset can be correctly attached while a different campaign remains unsuitable. The unchanged summary does not prove the exact edit failed or that every route is correct. Inspect the target and requested state to answer the execution question, then use the audit as a separate structural observation.
Operational and commercial evaluation should follow their own evidence. A route test can establish a specific handling observation, while a later report can show selected primary call conversions or value. Preserve the period and definitions. The asset's stored state should not be treated as a measured increase in useful enquiries. The record can connect the stages through the original objective while retaining their independent completion conditions. Colleagues can then understand why configuration is complete and another evaluation task still remains.
Resolve uncertain and partial results
An edit can be sent while complete verification remains unavailable. Reconcile the exact created asset or campaign relationship before replaying it. A blind creation retry can produce duplicate resources, so use the returned reference and intended fields where available. A broad asset list with similar numbers may not establish which resource belongs to the proposal. The result should distinguish an uncertain readback from a definite rejection. This directs the next action toward evidence rather than repetition.
For several requested actions, show each established and unresolved state. A new asset can be created while another detachment remains uncertain, or an association can change while a separate reporting read fails. Do not imply all operations rolled back because one result was incomplete. Equally, do not announce full completion from one successful step. The owner needs a precise handoff so the remaining request can continue from current state without accidental duplicate creation or broader changes than were approved.
Keep reconciliation separate from a new business decision. If the exact requested association is verified, a later operational concern may justify another proposal but does not make the original execution unperformed. If the association remains uncertain, an old message or remembered click is not proof of state. Resolve the account question with current evidence and the handling question with its own owner. This preserves a coherent sequence rather than mixing configuration uncertainty, measurement questions and commercial reconsideration into one generic failure.
Keep a durable call-route review process
The record should explain the campaign's call purpose, selected business route, operational owner, measurement definition and exact approved action. Retain the audit's trigger and coverage limitations where they affect interpretation. A primary call report and a card triggered by an eligible secondary action are different observations. An account-level presence result and a campaign-specific relationship check are also different. Clear scope lets the next reviewer understand why the team chose its route and what evidence established the current state.
Recurring review should follow meaningful changes such as staffing, service availability, new campaigns, route replacement and measurement revisions. Retrieve only the evidence needed for the current question. Routine analysis does not grant standing permission to edit every call asset, and scheduled automation is a separately configured workflow. A new conversational change needs a concrete proposal and confirmation. The team should maintain operational ownership rather than assume an enabled account association will preserve the correct handling arrangement indefinitely.
The call-asset audit guide provides related configuration context, while the Slack audit guide explains how the review can enter conversation. A completed in-house review should leave an established route, honest coverage evidence and a verified supported edit where one was approved. The useful outcome is a call path the team can explain and evaluate, rather than a presence pill that stands in for the number, staffing, reporting and commercial results together.