227 lines
8.9 KiB
TypeScript
227 lines
8.9 KiB
TypeScript
export type SolutionNavItem = {
|
||
label: string;
|
||
href: string;
|
||
};
|
||
|
||
export type SolutionCard = {
|
||
id: string;
|
||
eyebrow: string;
|
||
title: string;
|
||
href: string;
|
||
lead: string;
|
||
image: string;
|
||
imageAlt: string;
|
||
tags: string[];
|
||
};
|
||
|
||
export type SolutionPage = SolutionCard & {
|
||
slug: string;
|
||
summary: string;
|
||
stats: Array<{
|
||
value: string;
|
||
label: string;
|
||
}>;
|
||
workflow: string[];
|
||
capabilities: Array<{
|
||
title: string;
|
||
body: string;
|
||
}>;
|
||
scenarios: string[];
|
||
outputs: string[];
|
||
note?: string;
|
||
};
|
||
|
||
export const solutionNavItems: SolutionNavItem[] = [
|
||
{ label: "企业数字化解决方案", href: "/solutions/digital-enterprise" },
|
||
{ label: "新媒体内容分发智能体", href: "/solutions/media-distribution" },
|
||
{ label: "股市投研情报智能体", href: "/solutions/investment-research" },
|
||
{ label: "多平台自动运营智能体", href: "/solutions/agent-operations" },
|
||
];
|
||
|
||
export const solutionOverview = {
|
||
eyebrow: "企业方案",
|
||
title: "AI Agent 行业解决方案",
|
||
lead: "从通用企业数字化底座,到内容分发、投研情报与自动运营,把可重复的信息处理流程封装成可运行、可审计、可接入的业务智能体。",
|
||
};
|
||
|
||
const deliveryOutputs = [
|
||
"一对一部署 Agent",
|
||
"对接大模型",
|
||
"一对一指导",
|
||
"按需定制",
|
||
"稳定交付",
|
||
"24 小时持续运行",
|
||
];
|
||
|
||
const digitalEnterprisePage: SolutionPage = {
|
||
id: "digital-enterprise",
|
||
slug: "digital-enterprise",
|
||
eyebrow: "通用方案",
|
||
title: "企业数字化解决方案",
|
||
href: "/solutions/digital-enterprise",
|
||
lead: "将大模型能力嵌入 ERP、数据中台与协同办公流程,形成可落地的经营分析、合规风控与客户洞察能力。",
|
||
summary:
|
||
"面向企业已有系统和业务流程,将智能报告、知识问答、流程自动化和数据洞察能力接入日常经营,让 AI 成为可审计、可协同、可持续运行的企业能力底座。",
|
||
image: "/banner.png",
|
||
imageAlt: "企业数字化解决方案示意图",
|
||
tags: ["经营分析", "合规风控", "客户洞察"],
|
||
stats: [
|
||
{ value: "ERP", label: "业务系统接入" },
|
||
{ value: "BI", label: "经营分析看板" },
|
||
{ value: "Agent", label: "智能体流程编排" },
|
||
],
|
||
workflow: ["需求梳理", "系统接入", "模型编排", "流程上线", "持续优化"],
|
||
capabilities: [
|
||
{
|
||
title: "经营分析中枢",
|
||
body: "统一指标口径,自动生成经营看板、数据解读和管理层报告,减少人工汇总成本。",
|
||
},
|
||
{
|
||
title: "合规与风控助手",
|
||
body: "支持制度文档问答、合同要点提取、异常条款提示和风险复核流转。",
|
||
},
|
||
{
|
||
title: "客户成功洞察",
|
||
body: "从工单、通话记录和客户反馈中提炼风险信号、续约建议和跟进动作。",
|
||
},
|
||
{
|
||
title: "既有系统融合",
|
||
body: "围绕 ERP、数据中台、知识库和协同办公系统做轻量接入,不替代已有系统。",
|
||
},
|
||
],
|
||
scenarios: ["经营数据分析", "合同与制度核验", "客户续约洞察", "企业知识库问答"],
|
||
outputs: deliveryOutputs,
|
||
};
|
||
|
||
export const solutionPages: SolutionPage[] = [
|
||
digitalEnterprisePage,
|
||
{
|
||
id: "media-distribution",
|
||
slug: "media-distribution",
|
||
eyebrow: "新媒体方案",
|
||
title: "新媒体内容分发智能体",
|
||
href: "/solutions/media-distribution",
|
||
lead: "面向多平台内容运营团队,统一完成选题排期、内容生成、平台适配、账号发布与异常追踪。",
|
||
summary:
|
||
"把公众号、知乎、头条、百家号、CSDN、掘金等平台的发布规则和账号流程集中管理,让团队从反复搬运和格式调整中释放出来。",
|
||
image: "/solutions/media-distribution-final.png",
|
||
imageAlt: "新媒体内容分发智能体仪表盘示意图",
|
||
tags: ["内容编排", "多平台分发", "发布追踪"],
|
||
stats: [
|
||
{ value: "6+", label: "平台能力矩阵" },
|
||
{ value: "92%", label: "执行成功率看板" },
|
||
{ value: "7x24", label: "任务队列巡检" },
|
||
],
|
||
workflow: ["排期导入", "AI 生成", "平台适配", "安全发布", "数据回写"],
|
||
capabilities: [
|
||
{
|
||
title: "多平台内容适配",
|
||
body: "根据不同平台的标题、封面、标签、正文长度与链接规则,自动生成可发布版本。",
|
||
},
|
||
{
|
||
title: "账号与会话管理",
|
||
body: "统一管理多账号身份、登录状态、发布节奏与异常提醒,降低人工切换成本。",
|
||
},
|
||
{
|
||
title: "生成预览与人工确认",
|
||
body: "发布前集中预览标题、封面和正文,关键内容保留人工确认节点。",
|
||
},
|
||
{
|
||
title: "发布历史可追踪",
|
||
body: "沉淀发布记录、失败原因、平台反馈与任务日志,方便团队复盘和审计。",
|
||
},
|
||
],
|
||
scenarios: ["品牌内容矩阵运营", "知识型长文分发", "技术社区同步发布", "活动内容定时推送"],
|
||
outputs: deliveryOutputs,
|
||
},
|
||
{
|
||
id: "investment-research",
|
||
slug: "investment-research",
|
||
eyebrow: "投研方案",
|
||
title: "股市投研情报智能体",
|
||
href: "/solutions/investment-research",
|
||
lead: "面向投研、财经内容与股票社群场景,自动聚合公告、舆情、行情与信号,输出可追溯的机会卡片。",
|
||
summary:
|
||
"把公告快讯、社区讨论、行情异动和因子信号接入同一个情报中枢,帮助团队更快发现值得复核的信息线索。",
|
||
image: "/solutions/investment-research-final.png",
|
||
imageAlt: "股市投研情报智能体仪表盘示意图",
|
||
tags: ["公告雷达", "舆情热度", "信号复核"],
|
||
stats: [
|
||
{ value: "24h", label: "公告与舆情巡检" },
|
||
{ value: "S/A/B", label: "线索分层评分" },
|
||
{ value: "0 荐股", label: "合规定位" },
|
||
],
|
||
workflow: ["数据接入", "信息雷达", "因子判断", "机会卡片", "复盘反馈"],
|
||
capabilities: [
|
||
{
|
||
title: "信息雷达层",
|
||
body: "聚合公告、财经快讯、社区舆情、行情快照与回看因子,形成统一情报入口。",
|
||
},
|
||
{
|
||
title: "前置信号评分",
|
||
body: "按热度、时效、证据来源、利好利空与风险提示,对候选线索进行分层。",
|
||
},
|
||
{
|
||
title: "群消息与看板推送",
|
||
body: "把重要公告、异动线索和复核按钮推送到社群或内部看板,减少人工盯盘压力。",
|
||
},
|
||
{
|
||
title: "反馈闭环",
|
||
body: "沉淀用户反馈、关注股、误报原因与后续表现,用于优化下一轮信号判断。",
|
||
},
|
||
],
|
||
scenarios: ["股票社群信息推送", "财经内容选题发现", "投研线索初筛", "公告与舆情巡检"],
|
||
outputs: deliveryOutputs,
|
||
note: "本方案用于信息整理、线索发现与辅助分析,不提供荐股、收益承诺或证券投资建议。",
|
||
},
|
||
{
|
||
id: "agent-operations",
|
||
slug: "agent-operations",
|
||
eyebrow: "运营方案",
|
||
title: "多平台自动运营智能体",
|
||
href: "/solutions/agent-operations",
|
||
lead: "面向获客、曝光、招聘和私域运营场景,自动识别线索意图、生成回复、沉淀客户并触发人工复核。",
|
||
summary:
|
||
"把小红书、抖音、BOSS直聘、微信等平台的重复运营动作串成闭环,让 AI 先完成扫描、判断、回复草稿和客户入库。",
|
||
image: "/solutions/agent-operations-final.png",
|
||
imageAlt: "多平台自动运营智能体流程示意图",
|
||
tags: ["线索发现", "自动回复", "客户沉淀"],
|
||
stats: [
|
||
{ value: "4 类", label: "平台运营场景" },
|
||
{ value: "83%", label: "任务进度追踪" },
|
||
{ value: "CSV", label: "客户数据导出" },
|
||
],
|
||
workflow: ["线索发现", "意图识别", "自动触达", "客户入库", "持续跟进"],
|
||
capabilities: [
|
||
{
|
||
title: "线索发现与意图判断",
|
||
body: "扫描评论区、私信、候选人沟通和互动线索,判断是否值得进入跟进队列。",
|
||
},
|
||
{
|
||
title: "自动回复与触达",
|
||
body: "结合上下文生成回复草稿,支持自动执行或人工确认后执行。",
|
||
},
|
||
{
|
||
title: "客户库沉淀",
|
||
body: "把平台来源、需求标签、沟通状态与后续动作写入客户库,避免线索流失。",
|
||
},
|
||
{
|
||
title: "风控与人工复核",
|
||
body: "关键动作保留人工审核,支持频率限制、失败恢复、日志追踪与一键导出。",
|
||
},
|
||
],
|
||
scenarios: ["小红书评论找客", "抖音互动曝光", "招聘候选筛选", "微信私域跟进"],
|
||
outputs: deliveryOutputs,
|
||
},
|
||
];
|
||
|
||
export const solutionCards: SolutionCard[] = solutionPages;
|
||
|
||
export function getSolutionBySlug(slug: string) {
|
||
return solutionPages.find((solution) => solution.slug === slug);
|
||
}
|
||
|
||
export function getSolutionSlugs() {
|
||
return solutionPages.map((solution) => solution.slug);
|
||
}
|