Staffing and stock decisions are made against a number somebody guessed last Thursday. Demand Outlook replaces the guess with a projection that shows its work. It reads daily order counts from your history tables in BigQuery or Snowflake, contact counts by channel from Amazon Connect through GetMetricDataV2, the public holidays for your countries from the Nager holidays feed, and the forecast for your regions from Open-Meteo or the National Weather Service.
From those it projects each of the next fourteen days: orders, contacts by channel, and the holiday or weather effect applied to each. It proposes the projection as the planning baseline, written to your planning sheet and posted to the planning channel. A person approves the baseline before anyone plans against it.
This is a reference listing. It documents what Fibric would read from Demand Outlook and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.
Inputs
Daily order counts and revenue by channel from your history tables in BigQuery or Snowflake
CONTACTS_HANDLED and CONTACTS_ABANDONED by CHANNEL and QUEUE from Amazon Connect GetMetricDataV2, in DAY intervals
Public holidays by country and year from the Nager holidays feed, with no key required
Daily forecast variables such as temperature_2m, precipitation, and snowfall from Open-Meteo, up to sixteen days ahead
Seven-day forecasts in twelve-hour periods from the National Weather Service gridpoints endpoint for US locations
Last period's baseline and the actuals that followed, so the projection shows its own error
Proposed actions
Target capability: propose the fourteen-day baseline as rows in your planning sheet through spreadsheets.values.update
Target capability: propose the baseline summary in the planning Slack channel, with the holiday and weather adjustments listed
Target capability: propose a revised baseline mid-period when a forecast or holiday change moves a day beyond the tolerance you set
Target capability: propose a Jira task for the workforce or inventory owner when a projected day exceeds the capacity you recorded
Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.
What you can build
Two weeks of contacts for the scheduling team
Demand Outlook projects contacts by channel per day from Amazon Connect history and the warehouse, marks the two public-holiday days from the Nager feed, and proposes the baseline to the scheduling sheet.
Open-Meteo shows snowfall for three of the next five days in the main region. The operator applies the historical snow-day effect to orders and proposes a revised baseline to the planning channel.
A projected order day exceeds the pick capacity recorded for the warehouse. The operator proposes a Jira task to the inventory owner with the day, the projection, and the history behind it.
History tables with at least the prior year of daily orders and contacts, readable by the warehouse connector
An Amazon Connect instance the connector can query with GetMetricDataV2, for contact history and channel mix
Your countries and regions, so the holiday and forecast signals know what to fetch
A planning sheet and channel where the baseline is proposed, and a named owner who approves it
Authentication
Demand Outlook has no keys of its own. Warehouse reads go through the BigQuery or Snowflake connector, contact metrics through the Amazon Connect connector, holidays and weather through the signals, and writes through Google Sheets, Slack, and Jira.
Limits
GetMetricDataV2 returns the last three months and at most thirty-five days per request, so longer contact history comes from your warehouse.
Open-Meteo forecasts run sixteen days; the National Weather Service forecast runs seven. Days past the horizon carry only history and holidays.
It projects volume. It does not schedule staff, place purchase orders, or change a forecast someone else owns.
A projection is only as good as the history behind it. A channel launched last month has no seasonal pattern yet.
Access and pricing
Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.
The baseline: fourteen rows of projected orders and contacts, each with the history it drew on, the holiday flag, and the weather adjustment. You approve it as proposed or edit any day first. A mid-period revision is a separate proposal showing what moved.
What record does it leave?
Each baseline is kept with the history window it used, the holiday and forecast data as read, the method applied per day, who approved it, and the actuals recorded afterward. The next baseline shows the previous one's error by day.
Does it write the forecast into planning tools on its own?
No. It proposes the baseline to a sheet and a channel and waits. It never creates schedules, purchase orders, or forecasts in another system, and it never posts before approval.
Ask about Demand Outlook
Ask about the capabilities and requirements in this listing.
This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy