[laurentb]

How would that work considering Salesforce already has Quip ?

[jitl]

I think it would be great for both products if they were integrated tightly. The chat features in quip are barely used because they’re so anemic, and Slack is missing a document catalog UI, and, in a way, has gone to war with document catalogs because it wants chat to be the “center” of work. But this is often a mismatch for customers who view both as equally important.

[jasonv]

I use Slack and Quip and they’re not the same thing.

[laurentb]

really? I thought they were pretty much a direct competitor except with a different take on the whole idea. What's the use case for Quip then ?

[jitl]

Quip is a wiki. Use it to write and share documents. Slack is a communication tool. Use it to have conversations.

[noema]

At my job we use Quip strictly for collaborative design docs (i.e. architectural design, project scope, tutorials etc). Personally I don't think it can be a true wiki platform since it lacks robust indexing -- this is without doubt its biggest shortcoming.

[lobotryas]

Correct. Quip is not a wiki. I would call it an “opinionated and stripped-down version of GSuite with excellent collaboration support”. Quip also has chat stapled to it.

Slack is missing doc management/creation. Quip is missing a good chat solution. It’s almost like PB&J.

[Slartie]

A wiki? I thought it was an electric toothbrush!

[nateburke]

Quip competes with Office 365/Gsuite, not Microsoft Teams/Gchat.

[Irishsteve]

We used it as a google docs alternative