1
00:00:00,000 --> 00:00:01,300
Welcome to the deep dive.

2
00:00:01,300 --> 00:00:05,360
This is where we take the sources you've sent our way articles, research notes,

3
00:00:05,360 --> 00:00:07,680
and really dig in to find the core insights.

4
00:00:07,680 --> 00:00:08,060
Yeah.

5
00:00:08,060 --> 00:00:10,180
And today we're jumping into AUS ticket.

6
00:00:10,180 --> 00:00:14,640
It's a, well, a pretty popular open source support ticketing system.

7
00:00:14,640 --> 00:00:18,780
That's the one we've got material from the official AUS ticket GitHub repository,

8
00:00:18,780 --> 00:00:21,600
their main website, basically straight from the source.

9
00:00:21,600 --> 00:00:21,960
Right.

10
00:00:21,960 --> 00:00:27,520
And our goal here, our mission for this deep dive is to really unpack what

11
00:00:27,520 --> 00:00:30,520
AUS ticket is, you know, why so many people use it,

12
00:00:30,520 --> 00:00:34,680
how it actually works day to day and what makes it tick all based on the info

13
00:00:34,680 --> 00:00:35,160
we've got.

14
00:00:35,160 --> 00:00:36,920
And we really want to make this easy to follow.

15
00:00:36,920 --> 00:00:40,160
So even if you're totally new to support software,

16
00:00:40,160 --> 00:00:42,280
maybe new to open source entirely,

17
00:00:42,280 --> 00:00:45,160
you should get a really clear picture by the end.

18
00:00:45,160 --> 00:00:46,200
Think of it as a primer.

19
00:00:46,200 --> 00:00:46,520
Yeah.

20
00:00:46,520 --> 00:00:48,920
A quick way to get up to speed on AUS ticket.

21
00:00:48,920 --> 00:00:49,680
Exactly.

22
00:00:49,680 --> 00:00:51,480
Uh, before we properly kick off though,

23
00:00:51,480 --> 00:00:54,400
we should give a quick shout out to safe server.de.

24
00:00:54,400 --> 00:00:56,000
They're supporting this deep dive.

25
00:00:57,240 --> 00:01:00,680
Safe server focuses on hosting and helping businesses

26
00:01:00,680 --> 00:01:02,400
with their digital transformation.

27
00:01:02,400 --> 00:01:05,000
Like the source material actually puts it, uh,

28
00:01:05,000 --> 00:01:06,280
safe server commit safe.

29
00:01:06,280 --> 00:01:08,960
Um, does hosting these are software.

30
00:01:08,960 --> 00:01:15,840
So if that sounds interesting, check them out at www safe server.de.

31
00:01:15,840 --> 00:01:16,560
Okay.

32
00:01:16,560 --> 00:01:19,520
So AUS ticket, let's get into the meat of it.

33
00:01:19,520 --> 00:01:21,240
What's the fundamental problem.

34
00:01:21,240 --> 00:01:24,360
It's designed to fix looking at the sources.

35
00:01:24,520 --> 00:01:28,600
It seems to be all about handling customer support requests more, uh,

36
00:01:28,600 --> 00:01:29,920
effectively precisely.

37
00:01:29,920 --> 00:01:33,160
And the way it does that according to the sources is pretty smart.

38
00:01:33,160 --> 00:01:34,200
It's about consolidation.

39
00:01:34,200 --> 00:01:36,240
You know how support requests can come in from everywhere.

40
00:01:36,240 --> 00:01:36,480
Yeah.

41
00:01:36,480 --> 00:01:38,000
Email, phone calls, web forms.

42
00:01:38,000 --> 00:01:38,320
Yeah.

43
00:01:38,320 --> 00:01:39,080
It can get messy.

44
00:01:39,080 --> 00:01:39,680
Right.

45
00:01:39,680 --> 00:01:44,440
So AUS ticket, um, seamlessly pulls all of those emails, calls, logged by agents,

46
00:01:44,440 --> 00:01:45,640
web form submissions.

47
00:01:45,640 --> 00:01:48,280
It integrates them into one single web-based interface.

48
00:01:48,280 --> 00:01:49,920
Easy to use apparently.

49
00:01:49,920 --> 00:01:50,520
Uh, okay.

50
00:01:50,520 --> 00:01:54,000
So it's like a central command center for support, not just a basic inbox.

51
00:01:54,360 --> 00:01:55,120
Exactly.

52
00:01:55,120 --> 00:01:59,160
No more hunting through different email threads or trying to match up phone notes.

53
00:01:59,160 --> 00:02:01,560
The sources really hammer this home.

54
00:02:01,560 --> 00:02:07,760
The big benefit is managing, organizing, and archiving everything, every

55
00:02:07,760 --> 00:02:10,000
request, every response in one spot.

56
00:02:10,000 --> 00:02:14,000
Which leads to better accountability, I guess, for the team and the customer.

57
00:02:14,000 --> 00:02:15,280
Yeah, definitely.

58
00:02:15,280 --> 00:02:16,920
The team knows what needs doing.

59
00:02:16,920 --> 00:02:18,040
Nothing gets lost.

60
00:02:18,040 --> 00:02:21,560
And the customer feels like their issue is actually being tracked properly.

61
00:02:21,560 --> 00:02:22,960
Makes a big difference.

62
00:02:23,320 --> 00:02:26,080
And how does it stack up against other options out there?

63
00:02:26,080 --> 00:02:30,560
Well, the sources position it as a really attractive alternative, you know,

64
00:02:30,560 --> 00:02:34,480
compared to some of the higher cost systems that can be quite complex.

65
00:02:34,480 --> 00:02:38,720
They describe Osticket as simple, lightweight, reliable, and pretty

66
00:02:38,720 --> 00:02:39,840
easy to set up and use.

67
00:02:39,840 --> 00:02:41,120
Kind of hits a sweet spot.

68
00:02:41,120 --> 00:02:42,640
Simple and reliable is good.

69
00:02:42,640 --> 00:02:45,400
And the cost aspect, you mentioned higher cost systems.

70
00:02:45,400 --> 00:02:46,040
Ah, yes.

71
00:02:46,040 --> 00:02:48,400
Crucially, the sources are very clear.

72
00:02:48,400 --> 00:02:51,640
The open source version of Osticket is completely free.

73
00:02:51,880 --> 00:02:54,560
Free. That's obviously a huge draw for a lot of people, right?

74
00:02:54,560 --> 00:02:57,360
Small businesses, nonprofits, even larger orgs, maybe.

75
00:02:57,360 --> 00:02:58,320
Absolutely.

76
00:02:58,320 --> 00:03:00,000
It removes a major barrier.

77
00:03:00,000 --> 00:03:02,720
So, okay, let's walk through how it works in practice.

78
00:03:02,720 --> 00:03:05,560
The sources lay out a pretty straightforward flow for a

79
00:03:05,560 --> 00:03:07,200
typical support request.

80
00:03:07,200 --> 00:03:07,440
Right.

81
00:03:07,440 --> 00:03:08,360
Let's trace the journey.

82
00:03:08,360 --> 00:03:10,120
Where does it begin with the customer?

83
00:03:10,120 --> 00:03:10,840
Exactly.

84
00:03:10,840 --> 00:03:12,920
It starts with the user needing help.

85
00:03:12,920 --> 00:03:13,840
They create a ticket.

86
00:03:13,840 --> 00:03:18,800
And like we said, that could be through a web form, maybe sending an email, or

87
00:03:18,800 --> 00:03:22,630
even if they call, an agent can create the ticket for them right there in the

88
00:03:22,630 --> 00:03:23,000
system.

89
00:03:23,000 --> 00:03:23,280
Okay.

90
00:03:23,280 --> 00:03:27,440
So step one, the request comes in and becomes a ticket.

91
00:03:27,440 --> 00:03:27,840
Yeah.

92
00:03:27,840 --> 00:03:29,640
What happens then instantly?

93
00:03:29,640 --> 00:03:32,560
As soon as it hits the system, AUS ticket automatically saves it.

94
00:03:32,560 --> 00:03:33,560
So there's always a record.

95
00:03:33,560 --> 00:03:34,120
That's key.

96
00:03:34,120 --> 00:03:36,080
And then this is where the smarts come in.

97
00:03:36,080 --> 00:03:38,000
It can automatically assign that ticket.

98
00:03:38,000 --> 00:03:39,120
Assign it to who?

99
00:03:39,120 --> 00:03:43,840
To the right agent or maybe the right department or team based on rules you can set

100
00:03:43,840 --> 00:03:44,000
up.

101
00:03:44,000 --> 00:03:46,000
So it doesn't just sit in a big pile.

102
00:03:46,000 --> 00:03:46,520
Gotcha.

103
00:03:46,520 --> 00:03:47,280
It gets routed.

104
00:03:47,600 --> 00:03:49,880
So the agent gets notified and then play.

105
00:03:49,880 --> 00:03:52,320
Then the agent uses that web interface we mentioned.

106
00:03:52,320 --> 00:03:57,640
They can see all the ticket details, the user's history maybe, and communicate back

107
00:03:57,640 --> 00:03:59,840
and forth with the customer directly through the system.

108
00:03:59,840 --> 00:04:02,200
Everything gets logged in that one ticket thread.

109
00:04:02,200 --> 00:04:03,080
Okay.

110
00:04:03,080 --> 00:04:07,720
Notes, replies, status changes, all tracked together.

111
00:04:07,720 --> 00:04:08,200
Yeah.

112
00:04:08,200 --> 00:04:12,000
It keeps the whole resolution process visible and hopefully pretty efficient.

113
00:04:12,000 --> 00:04:13,320
That makes a lot of sense.

114
00:04:13,320 --> 00:04:17,000
It definitely sounds like it brings structure to what could be chaos.

115
00:04:17,400 --> 00:04:21,880
But beyond just managing the flow, what about specific features?

116
00:04:21,880 --> 00:04:24,400
The sources mentioned tons of awesome features.

117
00:04:24,400 --> 00:04:25,600
What stands out?

118
00:04:25,600 --> 00:04:26,360
Ah, yeah.

119
00:04:26,360 --> 00:04:27,680
They definitely pack a lot in.

120
00:04:27,680 --> 00:04:31,120
One thing the sources highlight, especially for managers, is the dashboard reports.

121
00:04:31,120 --> 00:04:31,480
Okay.

122
00:04:31,480 --> 00:04:32,000
What do they show?

123
00:04:32,000 --> 00:04:36,120
They give you a quick overview, like help desk stats at a glance, things like, you

124
00:04:36,120 --> 00:04:39,760
know, how many tickets are open, average response times, resolution rates.

125
00:04:39,760 --> 00:04:42,480
It's about seeing the health of your support operation quickly.

126
00:04:42,480 --> 00:04:43,680
Instant visibility.

127
00:04:43,680 --> 00:04:44,240
Nice.

128
00:04:44,680 --> 00:04:48,080
What about handling the incoming flood, keeping things organized?

129
00:04:48,080 --> 00:04:49,840
That's where ticket filters come in.

130
00:04:49,840 --> 00:04:53,640
The sources point to these as being really important for organization.

131
00:04:53,640 --> 00:04:54,960
You can set up rules.

132
00:04:54,960 --> 00:04:56,840
Rules based on what?

133
00:04:56,840 --> 00:05:01,200
Oh, like keywords in the subject who sent it, maybe the help topic they selected.

134
00:05:01,200 --> 00:05:05,000
Based on those rules, the ticket automatically gets sent to the right

135
00:05:05,000 --> 00:05:05,960
department or agent.

136
00:05:05,960 --> 00:05:09,600
Ah, so a billing question automatically goes to finance, for example.

137
00:05:09,600 --> 00:05:10,520
Exactly.

138
00:05:10,800 --> 00:05:14,960
Saves a ton of manual sorting and gets the ticket to the right person faster.

139
00:05:14,960 --> 00:05:17,880
The sources suggest this is a big time saver.

140
00:05:17,880 --> 00:05:18,720
I can see that.

141
00:05:18,720 --> 00:05:20,400
Less chance of errors too.

142
00:05:20,400 --> 00:05:22,560
What else helps customize things?

143
00:05:22,560 --> 00:05:24,960
There are configurable help topics.

144
00:05:24,960 --> 00:05:29,880
So instead of just help, users can pick something specific, like password reset

145
00:05:29,880 --> 00:05:32,960
or bug report or billing inquiry.

146
00:05:32,960 --> 00:05:34,520
And you can define those topics yourself.

147
00:05:34,520 --> 00:05:34,880
Yep.

148
00:05:34,880 --> 00:05:38,840
You tailor them to your business, makes it easier for users and gives agents

149
00:05:38,840 --> 00:05:40,080
immediate context.

150
00:05:40,320 --> 00:05:40,760
Smart.

151
00:05:40,760 --> 00:05:44,600
And is there anything for the customer side, a way for them to track things?

152
00:05:44,600 --> 00:05:45,400
Yes.

153
00:05:45,400 --> 00:05:46,760
The customer support portal.

154
00:05:46,760 --> 00:05:51,000
The sources describe it as a place where customers can log in, submit new tickets,

155
00:05:51,000 --> 00:05:53,680
check the status of their ongoing ones, see their history.

156
00:05:53,680 --> 00:05:54,240
Okay.

157
00:05:54,240 --> 00:05:56,360
So they're kept in the loop, empowers them a bit.

158
00:05:56,360 --> 00:05:56,960
Exactly.

159
00:05:56,960 --> 00:06:01,320
Builds transparency, which is usually good for customer relations as the sources

160
00:06:01,320 --> 00:06:01,720
imply.

161
00:06:01,720 --> 00:06:02,080
Right.

162
00:06:02,080 --> 00:06:06,760
And you mentioned something earlier, SLAs, service level agreements.

163
00:06:06,760 --> 00:06:07,720
Ah, yes.

164
00:06:07,720 --> 00:06:08,600
SLAs.

165
00:06:08,600 --> 00:06:09,880
Very powerful.

166
00:06:10,240 --> 00:06:13,720
The sources explain you can define your business hours and set targets for

167
00:06:13,720 --> 00:06:15,360
things like response times.

168
00:06:15,360 --> 00:06:19,400
Say you promise a four hour response for urgent issues.

169
00:06:19,400 --> 00:06:20,680
And the system tracks that.

170
00:06:20,680 --> 00:06:21,320
It does.

171
00:06:21,320 --> 00:06:24,840
It tracks tickets against those SLA targets and can even send alerts.

172
00:06:24,840 --> 00:06:28,240
If a deadline is approaching or missed, it helps ensure you meet your

173
00:06:28,240 --> 00:06:29,200
service commitments.

174
00:06:29,200 --> 00:06:29,640
Wow.

175
00:06:29,640 --> 00:06:30,200
Okay.

176
00:06:30,200 --> 00:06:32,080
That's quite a range of features.

177
00:06:32,080 --> 00:06:35,480
It really does sound like it covers the main basis for running support.

178
00:06:35,480 --> 00:06:39,240
Tons of awesome features seems about right based on the source descriptions.

179
00:06:39,240 --> 00:06:40,000
It really does.

180
00:06:40,000 --> 00:06:43,320
Now we're trying to keep this beginner friendly, but it's probably worth just

181
00:06:43,320 --> 00:06:45,000
briefly mentioning the technical side.

182
00:06:45,000 --> 00:06:47,040
What you'd need to run the self-hosted version.

183
00:06:47,040 --> 00:06:50,160
The GitHub source lists the requirements.

184
00:06:50,160 --> 00:06:50,520
Okay.

185
00:06:50,520 --> 00:06:50,880
Yeah.

186
00:06:50,880 --> 00:06:51,440
Good idea.

187
00:06:51,440 --> 00:06:52,280
Just the basics.

188
00:06:52,280 --> 00:06:54,080
No deep dive into server admin.

189
00:06:54,080 --> 00:06:54,600
Uh-huh.

190
00:06:54,600 --> 00:06:55,680
No, definitely not.

191
00:06:55,680 --> 00:06:56,560
Just the core bits.

192
00:06:56,560 --> 00:07:01,400
First, you need an HTTP server, a web server, standard stuff like Apache or

193
00:07:01,400 --> 00:07:02,480
Microsoft ISA.

194
00:07:02,480 --> 00:07:04,240
That's what serves up the web pages.

195
00:07:04,240 --> 00:07:04,480
Right.

196
00:07:04,480 --> 00:07:05,360
The web server software.

197
00:07:05,360 --> 00:07:05,800
Got it.

198
00:07:05,800 --> 00:07:07,400
Then it needs PHP.

199
00:07:07,640 --> 00:07:10,160
That's the programming language ASIC is actually written in.

200
00:07:10,160 --> 00:07:16,120
The sources recommend a pretty recent version, uh, 8.2 to 8.4 saying 8.4 is

201
00:07:16,120 --> 00:07:18,360
preferred shows they're keeping it modern.

202
00:07:18,360 --> 00:07:18,720
Okay.

203
00:07:18,720 --> 00:07:23,080
PHP, the language it runs on and what about all the data, the tickets, users,

204
00:07:23,080 --> 00:07:24,400
settings, where does that live?

205
00:07:24,400 --> 00:07:26,240
That needs a database specifically.

206
00:07:26,240 --> 00:07:30,080
The sources say a MySQL database version 5.5 or later.

207
00:07:30,080 --> 00:07:31,920
That's where everything gets stored.

208
00:07:31,920 --> 00:07:35,120
So web server, PHP, MySQL database.

209
00:07:35,120 --> 00:07:37,320
Those are the main ingredients from the source material.

210
00:07:37,680 --> 00:07:39,800
Sounds like a fairly standard setup for web applications.

211
00:07:39,800 --> 00:07:40,320
It is.

212
00:07:40,320 --> 00:07:45,040
Common technologies often free themselves, which ties back nicely to the

213
00:07:45,040 --> 00:07:46,120
open source aspect.

214
00:07:46,120 --> 00:07:50,400
The GitHub source clearly states it's licensed under the GPL2 license.

215
00:07:50,400 --> 00:07:50,560
Right.

216
00:07:50,560 --> 00:07:51,720
The open source license.

217
00:07:51,720 --> 00:07:54,920
And this is where the community aspect becomes really visible.

218
00:07:54,920 --> 00:07:55,280
Isn't it?

219
00:07:55,280 --> 00:07:57,520
The GitHub numbers you found are quite telling.

220
00:07:57,520 --> 00:07:58,440
They really are.

221
00:07:58,440 --> 00:08:04,160
The repository has over 3,400 stars, which is a decent

222
00:08:04,160 --> 00:08:06,360
indicator of interest and popularity.

223
00:08:06,360 --> 00:08:06,800
Okay.

224
00:08:07,000 --> 00:08:08,360
3.4 K stars.

225
00:08:08,360 --> 00:08:09,040
What else?

226
00:08:09,040 --> 00:08:12,360
Maybe more significantly over 1,700 forks.

227
00:08:12,360 --> 00:08:17,200
Remember a fork is someone making their own copy, often to tweak it or contribute

228
00:08:17,200 --> 00:08:19,360
back 1,700 forks.

229
00:08:19,360 --> 00:08:21,960
That suggests a lot of active engagement with the code.

230
00:08:21,960 --> 00:08:22,920
Wow.

231
00:08:22,920 --> 00:08:23,880
Yeah, that's substantial.

232
00:08:23,880 --> 00:08:24,920
People are really getting involved.

233
00:08:24,920 --> 00:08:26,000
What about contributors?

234
00:08:26,000 --> 00:08:27,400
People actually writing the code.

235
00:08:27,400 --> 00:08:33,360
The source mentions 119 core contributors plus another 105 mentioned elsewhere.

236
00:08:33,360 --> 00:08:36,520
That's, well, that's a lot of people putting time and skill into this.

237
00:08:36,520 --> 00:08:40,160
It really highlights the collaborative nature is not just one small team.

238
00:08:40,160 --> 00:08:41,800
A global effort, really.

239
00:08:41,800 --> 00:08:43,800
And that shows up in the language support too, right?

240
00:08:43,800 --> 00:08:44,440
Absolutely.

241
00:08:44,440 --> 00:08:47,800
The sources point out the interface is fully translatable and language

242
00:08:47,800 --> 00:08:48,800
packs are available.

243
00:08:48,800 --> 00:08:52,440
That's a direct result of the community people chipping in to make it usable

244
00:08:52,440 --> 00:08:53,000
everywhere.

245
00:08:53,000 --> 00:08:54,040
That's fantastic.

246
00:08:54,040 --> 00:08:57,160
It also looks like Ostiget itself builds on other open source work.

247
00:08:57,160 --> 00:08:57,720
Yes.

248
00:08:57,720 --> 00:09:02,040
The GitHub source lists some dependencies, things like font awesome for icons,

249
00:09:02,360 --> 00:09:08,920
Lamina's mail, probably for robust email handling and PDF, maybe for generating PDFs.

250
00:09:08,920 --> 00:09:10,920
It shows how these projects support each other.

251
00:09:10,920 --> 00:09:12,200
Part of that whole ecosystem.

252
00:09:12,200 --> 00:09:14,160
Yeah, that synergy is powerful.

253
00:09:14,160 --> 00:09:18,680
Now we've mostly talked about the free self hosted version, but you mentioned the

254
00:09:18,680 --> 00:09:23,160
website highlights another option for people who maybe don't want to manage servers.

255
00:09:23,160 --> 00:09:23,840
They do.

256
00:09:23,840 --> 00:09:26,600
There's a cloud hosted version called support system.

257
00:09:26,600 --> 00:09:29,360
Essentially it's Ostiget provided as a service.

258
00:09:29,360 --> 00:09:31,960
They handle the hosting, the updates, all the technical stuff for you.

259
00:09:32,040 --> 00:09:32,320
Okay.

260
00:09:32,320 --> 00:09:33,120
A managed option.

261
00:09:33,120 --> 00:09:34,560
Is there a way to try that out easily?

262
00:09:34,560 --> 00:09:34,960
Yep.

263
00:09:34,960 --> 00:09:40,160
The sources say they offer a 30 day free trial for support system and importantly,

264
00:09:40,160 --> 00:09:42,000
no credit card needed to start.

265
00:09:42,000 --> 00:09:42,840
Oh, that's good.

266
00:09:42,840 --> 00:09:44,960
Lowers the barrier to just give it a go.

267
00:09:44,960 --> 00:09:45,680
Exactly.

268
00:09:45,680 --> 00:09:48,320
Makes it easy to see if the cloud approach fits your needs better.

269
00:09:48,320 --> 00:09:52,240
So putting this all together, the features, the community, the free option, the

270
00:09:52,240 --> 00:09:52,560
cloud

271
00:09:52,560 --> 00:09:57,720
option, the sources also give some stats on just how big Ostiget reaches.

272
00:09:57,720 --> 00:09:59,040
And they're pretty impressive.

273
00:09:59,040 --> 00:10:00,120
They really are.

274
00:10:00,120 --> 00:10:01,720
It gives you a sense of the scale.

275
00:10:02,000 --> 00:10:06,400
The sources claim it's used by thousands of customers in over 190 countries.

276
00:10:06,400 --> 00:10:07,880
190 countries.

277
00:10:07,880 --> 00:10:08,480
Wow.

278
00:10:08,480 --> 00:10:09,480
That's nearly everywhere.

279
00:10:09,480 --> 00:10:11,320
It speaks volumes about its adaptability.

280
00:10:11,320 --> 00:10:16,640
And get this, they estimate over 5 million Ostiget users worldwide.

281
00:10:16,640 --> 00:10:19,360
5 million people interacting with the system.

282
00:10:19,360 --> 00:10:20,080
That's huge.

283
00:10:20,080 --> 00:10:26,000
And supporting those users over 15,000 businesses using Ostiget globally.

284
00:10:26,000 --> 00:10:31,400
15,000 businesses from tiny startups using the free version, presumably, to

285
00:10:31,400 --> 00:10:34,960
maybe much larger companies using hosted or heavily customized setups.

286
00:10:34,960 --> 00:10:36,880
That kind of adoption.

287
00:10:36,880 --> 00:10:39,920
It says a lot about trust and reliability, doesn't it?

288
00:10:39,920 --> 00:10:42,240
Especially for something handling customer support.

289
00:10:42,240 --> 00:10:43,160
It really does.

290
00:10:43,160 --> 00:10:46,280
And one of the sources sums it up well, quoting, thousands of

291
00:10:46,280 --> 00:10:50,520
customers in over 190 countries trust and use Ostiget for customer support.

292
00:10:50,520 --> 00:10:54,880
That word trust is key, especially with a significant open source component.

293
00:10:54,880 --> 00:10:55,160
Okay.

294
00:10:55,160 --> 00:10:58,640
So we've covered a lot based on these sources, what it is, how it works, the

295
00:10:58,640 --> 00:11:01,840
features, the tech basics, the community power, the cloud alternative,

296
00:11:01,840 --> 00:11:03,280
and this massive scale.

297
00:11:03,280 --> 00:11:04,440
Let's bring it back to the listener.

298
00:11:04,440 --> 00:11:06,080
Why should you care about all this?

299
00:11:06,080 --> 00:11:10,520
Well, maybe you're in a business where support feels like, you know, juggling

300
00:11:10,520 --> 00:11:14,040
emails and spreadsheets, and you're thinking there has to be a better way.

301
00:11:14,040 --> 00:11:17,200
This could be powerful, maybe even free.

302
00:11:17,200 --> 00:11:21,880
Or perhaps you're just interested in open source, how these big collaborative

303
00:11:21,880 --> 00:11:25,160
projects actually succeed and compete with commercial software.

304
00:11:25,160 --> 00:11:26,600
It's a fascinating case study.

305
00:11:26,760 --> 00:11:30,840
Or maybe you just appreciate clever solutions to common problems, seeing how

306
00:11:30,840 --> 00:11:33,840
software can streamline something complex like customer support.

307
00:11:33,840 --> 00:11:34,360
Right.

308
00:11:34,360 --> 00:11:39,040
What this deep dive really shows based on the sources is that there's this really

309
00:11:39,040 --> 00:11:43,080
robust, globally trusted tool out there for support.

310
00:11:43,080 --> 00:11:44,280
It's flexible.

311
00:11:44,280 --> 00:11:46,320
Host it yourself or use the cloud.

312
00:11:46,320 --> 00:11:49,800
And it's a testament to what open source collaboration can achieve.

313
00:11:49,800 --> 00:11:51,760
Which kind of leads to a final thought, doesn't it?

314
00:11:51,760 --> 00:11:51,960
Yeah.

315
00:11:51,960 --> 00:11:52,440
What's that?

316
00:11:52,440 --> 00:11:53,240
Think about it.

317
00:11:53,400 --> 00:11:57,560
How does a free community built project like this achieve such massive global

318
00:11:57,560 --> 00:12:03,360
reach, thousands of businesses, millions of users, features that stack up against

319
00:12:03,360 --> 00:12:05,160
expensive paid software?

320
00:12:05,160 --> 00:12:10,400
What does that success built on shared effort and open knowledge really tell us

321
00:12:10,400 --> 00:12:14,120
about the power of collaboration in building the tools that run our digital

322
00:12:14,120 --> 00:12:17,880
world, something to ponder maybe definitely something to think about.

323
00:12:19,200 --> 00:12:23,760
So that wraps up our deep dive into Ostigit for today based entirely on the

324
00:12:23,760 --> 00:12:25,080
source materials provided.

325
00:12:25,080 --> 00:12:30,200
We've looked at its purpose, features, community, scale, the whole picture.

326
00:12:30,200 --> 00:12:34,400
We really hope this gave you a solid, clear understanding of what Ostigit is

327
00:12:34,400 --> 00:12:37,120
all about and why it's such a significant tool out there.

328
00:12:37,120 --> 00:12:41,520
And a final thank you to safeserver.de for supporting this deep dive.

329
00:12:41,520 --> 00:12:45,120
Remember they specialize in hosting and digital transformation support.

330
00:12:45,120 --> 00:12:47,880
Check them out at www.safeserver.de.

331
00:12:48,200 --> 00:12:49,080
Thanks for tuning in.

332
00:12:49,080 --> 00:12:52,720
If Ostigit sounds like something that could help you, definitely worth exploring

333
00:12:52,720 --> 00:12:54,320
further based on what we've discussed.

334
00:12:54,320 --> 00:12:55,400
Till the next deep dive.